6cfa0c55d2
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.
60 lines
2.3 KiB
Markdown
60 lines
2.3 KiB
Markdown
---
|
|
name: msd:spec-phase
|
|
description: Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.
|
|
argument-hint: "<phase> [--auto] [--text]"
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Bash
|
|
- Glob
|
|
- Grep
|
|
- AskUserQuestion
|
|
requires: [discuss-phase, execute-phase, phase, plan-phase]
|
|
---
|
|
|
|
<objective>
|
|
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:**
|
|
1. Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
|
|
2. Scout the codebase — understand current state before asking questions
|
|
3. Run Socratic interview loop (up to 6 rounds, rotating perspectives)
|
|
4. Score ambiguity across 4 weighted dimensions after each round
|
|
5. Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
|
|
6. 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"
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/msd-core/workflows/spec-phase.md
|
|
@~/.claude/msd-core/templates/spec.md
|
|
</execution_context>
|
|
|
|
<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`.
|
|
</context>
|
|
|
|
<process>
|
|
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.
|
|
</process>
|
|
|
|
<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>
|