gsd-execute-phase
GitHub按波次并行执行阶段内的所有计划。协调器负责发现、依赖分析和分组，子代理独立处理各自计划。支持--wave指定波次、--gaps-only仅执行修复计划及--interactive交互式顺序执行等可选模式，确保高效且可控的端到端任务完成。
Trigger Scenarios
Install
npx skills add AjayIrkal23/agentic-mercy-10x --skill gsd-execute-phase -g -y
SKILL.md
Frontmatter
{
"name": "gsd-execute-phase",
"description": "Execute all plans in a phase with wave-based parallelization",
"allowed-tools": [
"Read",
"Write",
"Edit",
"Glob",
"Grep",
"Bash",
"Agent",
"TodoWrite",
"AskUserQuestion"
],
"argument-hint": "<phase-number> [--wave N] [--gaps-only] [--interactive] [--tdd]"
}
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 Nexecutes only WaveNfor 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> @$HOME/.claude/get-shit-done/workflows/execute-phase.md @$HOME/.claude/get-shit-done/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 WaveNin the phase. Use when you want to pace execution or stay inside usage limits.--gaps-only— Execute only gap closure plans (plans withgap_closure: truein 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 Nis active only if the literal--wavetoken is present in$ARGUMENTS--gaps-onlyis active only if the literal--gaps-onlytoken is present in$ARGUMENTS--interactiveis active only if the literal--interactivetoken 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-sdk query init.execute-phase and per-subagent <files_to_read> blocks.
Version History
- 581d130 Current 2026-07-19 09:09
