msd-core/commands/msd/execute-phase.md at next

Files

Jakub Zych 6cfa0c55d2 refactor: drop 12 runtimes, keep Claude, Codex, OpenCode, Cursor, ZCode, Antigravity

Removes kilo, kimi, kimi-code, copilot, windsurf, augment, trae, qwen, hermes,
cline, codebuddy and pi end to end: capability descriptors, installer branches
and converters (bin/install.js 14.9k -> 11.2k lines), TypeScript converters,
hook surfaces and runtime homes, review lanes qwen/kimi-code, the two pi
migrations, Kimi payload normalization in the hook guards, dead hostBehaviors
vocabulary, launcher home probes, fixtures, runtime-specific tests and the
prose that presented them as supported.

Installer output for the six kept runtimes is byte-identical to before the
prune. The Kimi tool-vocabulary tests in workflow-guard, read-guard and
read-injection-scanner are left in place pending a decision.

2026-10-06 20:02:40 +02:00

2.7 KiB

Raw Permalink 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>

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.7 KiB Raw Permalink Blame History

2.7 KiB

Raw Permalink Blame History