Files
msd-core/commands/gsd/execute-phase.md
Tom Boucher 71180983a0 fix(#3423): standardize on <required_reading>, retire the files_to_read emit tag (#3432)
* fix(#3423): standardize on required_reading, retire files_to_read emit tag

* test(#3423): flip tag assertions, extend consistency guard to spawner surfaces

* fix(#3423): sweep capabilities fragments, regen registry+skills, anchor executor test

* chore(#3423): acknowledge tag-rename emitted ripples and workflow growth

* chore(#3423): broaden emitted-ripple acknowledgment to all embedders

* chore(#3423): settle emitted-drift acks post-rebase (merge 3004/1689-owned keys)

* chore(#3423): drop stale ripple acks, ack execute-phase growth

* chore(#3423): restore pristine 3004 fragment, keep only consumed appends

* chore(#3423): backfill changeset pr number

* chore(#3423): settle emitted-drift acks post-merge (move code-review-fix ripple into 3190, tag-rename ripples into 3191/3297)

* chore(#3423): re-arm 3324 ack for execute-phase.md tag-rename ripple

* fix(#3423): trim 8 bytes from execute-phase model note to hold ADR-857 margin, re-arm 3370 ack for net +4 growth

---------

Co-authored-by: sim <sim@local>
2026-08-14 16:03:48 -04:00

2.9 KiB

name, description, argument-hint, effort, allowed-tools, requires
name description argument-hint effort allowed-tools requires
gsd:execute-phase Execute all plans in a phase with wave-based 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).