planning

# Planning Produce an executable plan, or strengthen an existing one. Planning alone produces no implementation edits. When the user asks to plan and implement, finish the plan and continue within the host's active mode and authorization. - **Create:** no plan exists; ground the approach in the repository and write the plan. - **Review:** a plan exists; verify its consequential claims and resolve concrete gaps in the file. - **Interview:** the user asks to be grilled or interviewed; explore decisions interactively. - **Split:** multiple independently deliverable outcomes need tickets with native dependency links. For architecture contracts use `codebase-architecture`; for code findings use `tidy`. ## References | File | Read when | |---|---| | `references/decision-briefs.md` | Presenting a consequential decision to the human: measuring options, previews, recording the answer | | `references/interrogation-protocol.md` | Choosing which question to ask about an unresolved choice, or the user requested an interview | | `references/doc-grounding.md` | ADRs, specifications, or library docs constrain the approach | | `references/handoff-plans.md` | Another session or person will execute the plan | | `references/plan-quality-rubric.md` | Reviewing completeness, feasibility, scope, testability, risk, and assumptions | | `references/questioning-framework.md` | A review gap needs a focused user question | | `references/claim-verification.md` | A plan claim can be checked against co...