gsd-plan-phase

To generate a PLAN.md, read inputs from ROADMAP.md, REQUIREMENTS.md, and CONTEXT.md, then translate them into a structured plan with task breakdowns, verification steps, and a rollback section. The output serves as a verifiable blueprint for execution.

Structuring a planning phase task breakdown requires mapping requirements coverage, defining per-task file changes, and enforcing nine quality gates. This ensures the PLAN.md passes threat modeling and verification checks before review.

Yes, you need ROADMAP.md, REQUIREMENTS.md, and CONTEXT.md to create a project plan. These input files provide the foundational goals and constraints needed to generate a comprehensive PLAN.md with accurate task details.

Requirements mapping in PLAN.md generation works by reading REQUIREMENTS.md and translating each item into specific task breakdowns. It ensures full coverage by linking every requirement to verifiable per-task details and verification steps.

A planning phase threat model and rollback strategy should include potential security risks mapped during planning and specific recovery steps. This is enforced as a mandatory section before the PLAN.md can pass its quality gates.

Your PLAN.md planning workflow fails quality gates if it lacks required sections like goal, requirements coverage, task breakdown, verification steps, threat model, or rollback. The exit condition requires passing all nine quality dimensions and a formal review.