mcpField
G
gsd-execute-phase

gsd-execute-phase

github.com/open-gsdAgent workflows11.0k440 installsUpdated today
Repository

About gsd-execute-phase

A skill for carrying out GSD plans within a phase. It keeps orchestration focused on discovering plans, mapping dependencies, and grouping work into waves, while subagents execute individual plans.

Key features

  1. 01Finds phase plans and analyzes dependencies
  2. 02Groups work into dependency-based waves
  3. 03Dispatches subagents in parallel
  4. 04Supports selecting a wave
  5. 05Preserves phase verification and completion

Use cases

  1. 01Running multiple plans in a phase concurrently
  2. 02Executing phase work in stages
  3. 03Running a selected wave within usage limits

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/open-gsd/gsd-core --skill gsd-execute-phase

After installing, type/gsd-execute-phasein Claude Code to confirm it loaded.

Details

From the project README

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

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 the <arguments> block
  • If a documented flag is absent from the <arguments> block, 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: the `` block

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> block
  • 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).

Comments

Markdown supported