msd-core/commands/msd/execute-phase.md at 12ee75a509cbfd8fe2ae2871056fa81777d7dcf5

Files

Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)

Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.

2026-10-06 01:47:40 +02:00

2.9 KiB

Raw Blame History

name, description, argument-hint, effort, allowed-tools, requires

name

description

argument-hint

effort

allowed-tools

requires

msd:execute-phase

SDD phase execution — execute all plans in a phase with dependency-aware wave parallelization

<phase-number> [--wave N] [--gaps-only] [--interactive] [--tdd]

max

Read

Write

Edit

Glob

Grep

Bash

Agent

TodoWrite

AskUserQuestion

phase

verify-work

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.

<execution_context> @~~/.claude/msd-core/workflows/execute-phase.md @~~/.claude/msd-core/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>

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 msd-tools query init.execute-phase and per-subagent <required_reading> blocks.

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

2.9 KiB Raw Blame History

2.9 KiB

Raw Blame History