---
title: Commit the planning folder with your code
description: Keep specs, stories, and tasks in the same commits as the code they describe, so every session and teammate reads the same plan.
url: https://openplanr.dev/docs/tips/commit-the-planning-folder
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/prompts/audit-plan-drift.md
  - https://openplanr.dev/docs/prompts/clarify-acceptance-criteria.md
  - https://openplanr.dev/docs/prompts/pick-the-sprint.md
---

# Commit the planning folder with your code

Keep specs, stories, and tasks in the same commits as the code they describe, so every session and teammate reads the same plan.

The planning folder, `.planr/`, is meant to be committed. Specifications, user stories, tasks, and provenance live there, reviewed and versioned like code.

When the plan changes in the same pull request as the code, a reviewer sees both: what the task asked for and what the change did. The next session, the next teammate, and the next agent start from the version of the plan that matches the code they check out.

To stop using the planning files in a project, delete the folder by hand.