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