meridianspec-phaselisted

# /meridian:spec-phase — Spec Phase Type Clarifies WHAT a phase delivers through a Socratic interview loop with quantitative ambiguity scoring. Produces `SPEC.md` in the phase artifact directory with falsifiable requirements locked before implementation decisions begin. **Position in workflow:** `spec-phase → discuss-phase → plan-phase → execute-phase` ## Arguments - (no args) — spec the current pending/planned phase - `--phase <id>` — spec a specific phase by ID - `--auto` — skip interview if ambiguity already ≤ 0.20; otherwise Claude selects best answers - `--skip-spec` — bypass gate warning in /meridian:plan (emergency only) ## Keywords spec, specification, requirements, clarify, ambiguity, scope, boundaries, falsifiable, what, deliverable, acceptance criteria, pre-plan, contract ## Ambiguity Model | Dimension | Weight | Minimum | What it measures | |-----------|--------|---------|-----------------| | Goal Clarity | 35% | 0.75 | Is the outcome specific and measurable? | | Boundary Clarity | 25% | 0.70 | What's in scope vs out of scope? | | Constraint Clarity | 20% | 0.65 | Performance, compatibility, data requirements? | | Acceptance Criteria | 20% | 0.70 | How do we know it's done? | `ambiguity = 1.0 − (0.35×goal + 0.25×boundary + 0.20×constraint + 0.20×acceptance)` **Gate:** ambiguity ≤ 0.20 AND all dimensions ≥ minimums → write SPEC.md. ## Procedure ### Step 1: Find Target Phase ```bash PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c "