The Phase Loop
The core GSD workflow: discuss → plan → execute → verify. How the loop works and why each phase matters.
beginnerOverview
GSD breaks work into phases — a deployment setup phase, a feature phase, a polish phase. Each phase follows the same loop: discuss first to shape the work, plan to decompose it, execute to build it, verify to confirm it’s done. The loop repeats for every phase, keeping each increment focused and reviewable.
Discuss
The discuss phase is where you and the agent clarify requirements, make architectural decisions, and lock choices before any code is written. Skipping discuss means the agent makes all decisions without your input — you end up reviewing surprises instead of confirming expectations.
$ /gsd:discuss-phase 1 Plan
The agent creates numbered PLAN.md files in .planning/phases/ with wave-organized tasks. Each plan is a self-contained execution prompt with enough context that the executor doesn’t need to explore the codebase independently.
$ /gsd:plan-phase 1 Execute
The agent works through each plan in wave order. Autonomous tasks run without interruption; checkpoint tasks pause and ask for your decision or verification before continuing.
$ /gsd:execute-phase 1 Verify
The agent checks all requirements are met and creates a VERIFICATION.md with any gaps found. Gaps are a prioritised list of what to address before calling the phase done — not a sign that something went wrong.
$ /gsd:verify-work 1 The Loop Repeats
After verification, start the next phase with the same four steps. Each phase builds on the previous one, accumulating context and momentum as the project grows.