From gsd
Executes all plans in a phase using wave-based parallelization, analyzing dependencies, grouping into waves, and spawning subagents. Supports --wave, --gaps-only, --interactive flags.
npx claudepluginhub jnuyens/gsd-plugin --plugin gsdThis skill is limited to using the following tools:
<objective>
Orchestrates wave-based parallel execution of all plans in a development phase, analyzing dependencies, grouping into waves, spawning subagents, and handling git branches if configured.
Executes individual phases of implementation plans as autonomous background sub-agents, performing pre-flight checks, file changes, and automated verifications.
Orchestrates parallel execution of phase build plans via subagents, manages task dependencies by waves, commits atomically. For PBR workflow after planning.
Share bugs, ideas, or general feedback.
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$ARGUMENTS, treat it as inactiveContext budget: ~15% orchestrator, 100% fresh per subagent.
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/execute-phase.md @${CLAUDE_PLUGIN_ROOT}/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 $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 $ARGUMENTSContext files are resolved inside the workflow via gsd-sdk query init.execute-phase and per-subagent <files_to_read> blocks.
<output_format>
When this workflow completes, emit a Next Up continuation block following the pattern in references/continuation-format.md:
## ✓ Phase N Complete with plan/task tally)## ▶ Next Up heading with the next likely command`/clear` then: before the command/clear is safe — /gsd:resume-work restores position from HANDOFF.json if you change your mind)Phase boundaries are the highest-value places to clear context — the accumulated execution conversation rarely informs the next phase, and /clear resets the prompt cache cleanly. Always suggest it on completion.
</output_format>