plan-mode

To create an auditable execution plan, describe your coding goal and constraints to generate a canonical plan at plans/<slug>.md with explicit success criteria, risk documentation, and a required approval gate before any repo edits occur.

Handling ambiguous requirements requires a design-first planning workflow that presents 2-3 options with trade-offs and a recommended path, aligning changes with your risk tolerance before gating all repository edits until explicit approval is granted.

Governance-driven development enforces approval gates by blocking repository edits during the planning phase, documenting decisions in a canonical plan file, and requiring explicit user approval to transition into Execute Mode for implementation.

Yes, you can document rollback strategies and risk management by generating a final plan that includes explicit risk documentation, success criteria, and rollback procedures within the plans/<slug>.md file before implementation begins.

You need a design-first planning workflow when requirements are vague, cross-file changes are likely, or explicit governance and approval gates are required before implementation to reduce ambiguity and risk in coding projects.

Yes, plan-mode operates without external dependencies or component integrations, independently converting vague requests into a final plans/<slug>.md file containing trade-off options, success criteria, and an explicit approval gate.