gsd-execute-phase

<objective> Execute all plans in a phase using wave-based parallel execution.

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

• 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> Phase: $ARGUMENTS

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

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

<process> Execute end-to-end. Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing). </process>