gsd-plan-phase

To create an executable roadmap phase plan, you need a workflow that normalizes phase input and routes it through research, planning, and verification. This produces a structured PLAN.md ready for execution with acceptance-driven validation.

Adding research and verification to phase planning requires a coordination loop between a planner and a checker. This approach iteratively rechecks the produced plan against validation criteria until it passes or reaches a maximum number of attempts.

Yes, you can skip research and generate a phase plan directly. The workflow supports refreshing phase research before planning when needed, or routing directly to planning when research is already complete or unnecessary.

Phase planning supports optional RESEARCH.md handling, allowing the workflow to incorporate existing research documents. This ensures the generated plan builds upon previously gathered context through argument parsing and normalization.

When a phase plan fails verification, the system applies iterative failure recovery. It rechecks the plan against a checker and regenerates it until the plan passes validation or reaches a maximum number of attempts.

You need acceptance-driven plan generation for engineering workflows when a roadmap phase requires a structured PLAN.md with validated acceptance criteria. This ensures phase-specific breakdowns are actionable and less error-prone before execution.