Gsd:execute Phase Agent Skill

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

</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: $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-sdk query init.execute-phase and per-subagent <files_to_read> blocks.

</context>

<process>

Execute the execute-phase workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/execute-phase.md end-to-end.

Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).

</process>

<output_format>

When this workflow completes, emit a Next Up continuation block following the pattern in references/continuation-format.md:

• Show completion status (e.g., ## ✓ Phase N Complete with plan/task tally)
• Emit a ## ▶ Next Up heading with the next likely command
• Use /clear then: before the command
• Include a parenthetical: *(/clear is safe — /gsd:resume-work restores position from HANDOFF.json if 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 — the accumulated execution conversation rarely informs the next phase, and /clear resets the prompt cache cleanly. Always suggest it on completion.

</output_format>