thecomputer07/qsd-execute-phase

<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> @$HOME/.claude/qsd/workflows/execute-phase.md @$HOME/.claude/qsd/references/ui-brand.md </execution_context>

<preflight_research_ingestion> Before fanning out subagents, check for pre-flight research output for this phase:

ls .planning/research/preflight-<phaseId>-*.md 2>/dev/null | tail -1

If a matching file exists, Read it and pass a short summary (3–5 bulleted findings with their — [source](url) citations preserved) into the spawn prompt of each executing subagent under an "Ambient pre-flight context" subsection. This mirrors how subagents already receive RESEARCH.md summaries.

Guard: Inspect the YAML frontmatter first. Skip the file (do NOT include it) when toggle_mode: off — defensive check; should never occur under normal flow.

No file present: Continue execution without preflight context (default-OFF path, workflow.preflight_research: off) — not an error.

Toggle documented at @$HOME/.claude/qsd/skills/qsd-settings/SKILL.md#preflight_research_toggle. </preflight_research_ingestion>

<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 qsd-tools init execute-phase and per-subagent <files_to_read> blocks. </context>

<process> Execute the execute-phase workflow from @$HOME/.claude/qsd/workflows/execute-phase.md end-to-end. Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing). </process>