Spec-Driven Delivery

THE /m:* PIPELINE

An interactive working drawing of spec-driven delivery for Claude Code — refine, plan, implement, review, iterate.

One command — /m:develop — drives every change through five gated phases, each running as a discrete Skill invocation behind a marker-file gate. The gates are hooks, not honor rules — no phase starts until the previous one proves it finished. Support stages feed project memory; expert modes clip onto the work.

Dwg No
M-001
Rev
A
Date
2026-06-09
Scale
NTS
Gates
Hook-enforced phases
Review
Blind lenses + judge
Models
Opus · Sonnet · Haiku + Codex 5.5
Memory
Per-repo .m/ state

Key — Components

pipeline support expert gate

Key — Linework

handoff · stage → stage memory feed · writes .m/ expert attach · clips onto a stage flow · left → right

How to read this sheet

  • SELECT any component — its full specification opens as a detail.
  • HOVER or FOCUS a card — its wiring inks to full strength.
  • ARROW KEYS walk the spine · ↓ enters a stage's gates · ESC closes the detail.

Support

feed project memory · .m/

Six utilities that build and feed the project's .m/ memory — the state every pipeline stage reads.

Expert modes

clip onto the work

Five expert lenses. Two run by hand; three load themselves when matching files are edited.

.m/  project memory
INDEX · TASKS · PROGRESS · GAPS · RESEARCH — read by every stage