Tip · Plan
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.
Related prompts
Audit the plan for drift
Check that stories, tasks, statuses, and references in the planning folder still agree.
Pin down acceptance criteria before planning
Turn loose requirements into observable criteria with stable IDs before anyone plans the work.
Pick the next sprint against the real code
Refine the open backlog and select what fits capacity and the release cut.