msd-core/commands/msd/spec-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.3 KiB

Raw Permalink Blame History

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

name

description

argument-hint

allowed-tools

requires

msd:spec-phase

Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.

<phase> [--auto] [--text]

Read

Write

Bash

Glob

Grep

AskUserQuestion

discuss-phase

execute-phase

phase

plan-phase

Clarify phase requirements through structured Socratic questioning with quantitative ambiguity scoring.

Position in workflow: spec-phase → discuss-phase → plan-phase → execute-phase → verify

How it works:

Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
Scout the codebase — understand current state before asking questions
Run Socratic interview loop (up to 6 rounds, rotating perspectives)
Score ambiguity across 4 weighted dimensions after each round
Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
Commit SPEC.md — discuss-phase picks it up automatically on next run

Output: {phase_dir}/{padded_phase}-SPEC.md — falsifiable requirements that lock "what/why" before discuss-phase handles "how"

<execution_context> @~~/.claude/msd-core/workflows/spec-phase.md @~~/.claude/msd-core/templates/spec.md </execution_context>

Phase number: $ARGUMENTS (required)

Flags:

--auto — Skip interactive questions; Claude selects recommended defaults and writes SPEC.md
--text — Use plain-text numbered lists instead of TUI menus (required for /rc remote sessions)

Context files are resolved in-workflow using init phase-op.

Execute end-to-end.

MANDATORY: Read the workflow file BEFORE taking any action. The workflow contains the complete step-by-step process including the Socratic interview loop, ambiguity scoring gate, and SPEC.md generation. Do not improvise from the objective summary above.

<success_criteria>

Codebase scouted for current state before questioning begins
All 4 ambiguity dimensions scored after each interview round
Gate passed: ambiguity ≤ 0.20 AND all dimension minimums met
SPEC.md written with falsifiable requirements, explicit boundaries, and acceptance criteria
SPEC.md committed atomically
User knows they can now run /msd:discuss-phase which will load SPEC.md automatically </success_criteria>

2.3 KiB Raw Permalink Blame History

2.3 KiB

Raw Permalink Blame History