Planr Plan

Use this skill to write an execution contract, not a design memo.

A planr-plan is invalid if it skips the real code, omits per-phase checklists, leaves verification vague, or treats completion as something later agents can assume instead of prove.

CLI-First Rule

• Read ../planr-shared.md first.
• If .planr/project/*.md is missing or still generic starter text, run ./.planr/tooling/planr project init, then inspect the target repo and rewrite those files before making strong architecture or ownership decisions.
• Use ./.planr/tooling/planr plan new ... to scaffold new plan files instead of hand-writing boilerplate.
• There is no general plan-update command today. After scaffolding, edit the existing plan body directly.

Required Inputs

• the user request, task doc, bug doc, or review finding that the plan is based on
• the existing implementation files likely to own the change
• adjacent tests and architecture docs when ownership or boundaries matter
• nearby .planr/plans/*.plan.md examples when creating a new plan shape from scratch