Drafting Plans

A plan is an implementation map, not a record of planning ceremony. Make it resumable and specific while including only sections the work needs.

Start With Evidence

Inspect existing plan conventions and relevant code, docs, schemas, configuration, issue, or PR context before naming contracts or commands.
Update an existing plan in place when it already owns the work.
Put the plan where the user asked. Preserve repository metadata and formatting conventions; do not invent frontmatter, lifecycle fields, or dates when the repository does not require them.
Verify cheap, drift-prone facts before presenting them as current state.

Follow repository convention first. Otherwise use the smallest useful subset of: