Execute a development phase by grouping plans into waves, sets of tasks that can run together based on dependencies. Collect results, verify completion, and update progress, with options to run a selected wave or work sequentially with checkpoints.
SDD phase execution — execute all plans in a phase with dependency-aware wave parallelization
Review the instructions the agent will receive before you install.
<arguments>$ARGUMENTS</arguments>
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.
Optional wave filter:
--wave N executes only Wave N for pacing, quota management, or staged rolloutFlag handling rule:
<arguments> block<arguments> block, treat it as inactiveContext budget: ~15% orchestrator, 100% fresh per subagent. </objective>
<execution_context>
@/.claude/gsd-core/workflows/execute-phase.md
@/.claude/gsd-core/references/ui-brand.md
</execution_context>
<runtime_note>
Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API.
</runtime_note>
Available optional flags (documentation only — not automatically active):
--wave N — Execute only Wave N in the phase. Use when you want to pace execution or stay inside usage limits.--gaps-only — Execute only gap closure plans (plans with gap_closure: true in frontmatter). Use after verify-work creates fix plans.--interactive — Execute plans sequentially inline (no subagents) with user checkpoints between tasks. Lower token usage, pair-programming style. Best for small phases, bug fixes, and verification gaps.Active flags must be derived from the <arguments> block:
--wave N is active only if the literal --wave token is present in the <arguments> block--gaps-only is active only if the literal --gaps-only token is present in the <arguments> block--interactive is active only if the literal --interactive token is present in the <arguments> blockContext files are resolved inside the workflow via gsd-tools query init.execute-phase and per-subagent <required_reading> blocks.
</context>
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add tests to a completed development phase using its records and implementation. Review the proposed coverage, then generate unit tests for individual components and browser tests for full workflows, verify them, and commit the test files.
Prepare an AI-SPEC.md design agreement for an AI development phase. The skill coordinates framework selection, documentation and domain research, and evaluation planning so the phase has a defined technical direction and assessment strategy.
Run an audit, separate findings that can be fixed automatically from those needing manual work, and apply eligible fixes with tests and separate commits. Use severity filters, a finding limit, or a classification-only dry run.
Audit a development milestone before archiving it by checking requirements, connections between phases, and complete user flows. It reads existing verification reports and gathers technical debt and deferred gaps to assess whether the original completion criteria were met.
Audit acceptance tests, which check whether features meet user needs, and verification records across project phases. Compare outstanding items with the codebase, flag outdated documentation, and produce a prioritized plan for human testing.
Run remaining GSD project phases through discussion, planning, and execution, while recording progress and phase documents. You can limit the phase range or keep decisions interactive; after all phases finish, the workflow audits and closes the milestone.