Files
msd-core/commands/gsd/execute-phase.md
Tom Boucher d29b50d696 fix(#4051): route specific intents first and confirm before dispatch in --do (#4289)
* test(#4051): pin freeform routing specificity contract in do.md

* fix(#4051): order freeform routing specific-first, confirm before dispatch, argument-aware forwarding

* fix(#4051): regenerate FEATURES.md, satisfy docs-guard on new routing test

Emitted-Drift-Ack-Growth: do.md — deliberate growth: specific-first routing table (code-review, plan review, ui-review, secure-phase, audit, docs-update, phase CRUD rows), a REQ-DO-03 confirm step, and argument-hint-aware dispatch.

* chore(#4051): fold regression into non-bug-prefixed test filename per lint-regression-test-names

* fix(#4051): review fixes — em-dash description style, split audit-fix route

* chore(#4051): sync skill mirrors of execute-phase/phase descriptions

* chore(#4051): add changeset (pr backfill to follow)

* chore(#4051): backfill PR 4289 in changeset

---------

Co-authored-by: sim <sim@local>
2026-09-04 17:19:16 -04:00

2.9 KiB

name, description, argument-hint, effort, allowed-tools, requires
name description argument-hint effort allowed-tools requires
gsd:execute-phase SDD phase execution — execute all plans in a phase with dependency-aware wave parallelization <phase-number> [--wave N] [--gaps-only] [--interactive] [--tdd] max
Read
Write
Edit
Glob
Grep
Bash
Agent
TodoWrite
AskUserQuestion
phase
verify-work
Execute all plans in a phase using wave-based parallel execution.

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 rollout
  • phase verification/completion still only happens when no incomplete plans remain after the selected wave finishes

Flag handling rule:

  • The optional flags documented below are available behaviors, not implied active behaviors
  • A flag is active only when its literal token appears in $ARGUMENTS
  • If a documented flag is absent from $ARGUMENTS, treat it as inactive

Context budget: ~15% orchestrator, 100% fresh per subagent.

<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>

Phase: $ARGUMENTS

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 $ARGUMENTS:

  • --wave N is active only if the literal --wave token is present in $ARGUMENTS
  • --gaps-only is active only if the literal --gaps-only token is present in $ARGUMENTS
  • --interactive is active only if the literal --interactive token is present in $ARGUMENTS
  • If none of these tokens appear, run the standard full-phase execution flow with no flag-specific filtering
  • Do not infer that a flag is active just because it is documented in this prompt

Context files are resolved inside the workflow via gsd-tools query init.execute-phase and per-subagent <required_reading> blocks.

Execute end-to-end. Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).