Writing Plans

A plan request authorizes creating or revising the plan artifact, not implementation. Execute the plan only when the user requests it or an active workflow already authorizes the work.

Ground the Plan

Inspect relevant repository evidence before asking questions. Ask at most one question when proceeding would require a risky guess; otherwise state only assumptions and unknowns that affect execution or validation.

Save a drafted plan to the repository unless the user requests chat-only output. Default to docs/plans/YYYY-MM-DD_<topic>-plan.md with a concise lowercase kebab-case topic, and update an existing plan in place during execution.

Structure the Plan

Always include Goal, Plan, and Completion Checklist. Add only useful optional sections from this list: