gsd-plan-phase

Automate phase planning by invoking the workflow with a phase number to coordinate research, planning, and verification, producing a PLAN.md output. It operates within a gated loop, iterating until criteria are met or maximum iterations are reached.

The gated loop verification works by spawning a planner and a checker to validate the phase planning output. It iterates through validation gates until success criteria are met or the loop reaches the maximum iteration limit.

You do not need to provide a phase number to start the end-to-end planning workflow. Invoking the skill without a phase number auto-detects the next unplanned phase and determines scope using provided execution context.

You can control research and verification steps during phase orchestration by using optional flags. These flags allow you to toggle research, gaps, and verification to tailor the workflow to your specific planning context.

The best way to handle phase context inputs is to provide execution context and phase input directly. The workflow reads these inputs to tailor the PLAN.md output for each specific roadmap phase.

If the plan checker fails verification multiple times, the workflow continues iterating until success criteria are met or the maximum iteration limit is reached. The gated loop preserves validation and routing throughout this process.