execute-phase
Execute all plans in a phase with wave-based parallelization
SKILL.mdskills/execute-phase/SKILL.md
GitHub<objective>
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 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: a flag is active only when its literal token appears in $ARGUMENTS; documented-but-absent flags are inactive.
Context budget: ~15% orchestrator, 100% fresh per subagent. </objective>
<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> <context> Phase: $ARGUMENTSAvailable 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.
A flag is active only if its literal token (--wave, --gaps-only, --interactive) is present in $ARGUMENTS. If none appear, run the standard full-phase execution flow with no flag-specific filtering. Do not infer a flag is active just because it is documented here.
Context files are resolved inside the workflow via bm-sdk query init.execute-phase and per-subagent <files_to_read> blocks.
</context>
- Show completion status (e.g.,
## ✓ Phase N Completewith plan/task tally) - Emit a
## ▶ Next Upheading with the next likely command - Use
`/clear` then:before the command - Include a parenthetical: (
/clearis safe —/gsd:resume-workrestores position fromHANDOFF.jsonif you change your mind) - Add an "Also available:" section with 1-3 alternatives where relevant
Phase boundaries are the highest-value places to clear context. Always suggest /clear on completion.
</output_format>