spec

/build — Gate 1.5, the construction layer after /spec. It reads the authoritative SPEC.md (+ .spec/ gates, Decision Log, knowledge) and constructs the code from it, regenerating the design/tasks plan EPHEMERALLY each run (never enshrined as a source of truth, so it can't drift). It closes construction only when each targeted requirement's acceptance holds AND the load-bearing gates are green (probes re-run). On a spec-vs-reality conflict it stops and routes back to /spec — it never silently edits the spec. Default surface: propose-then-apply with checkpoints. Resumable.

/spec — the project's process-management Gate 1. One repeatable command (like /init, but for the living specification). The AI plays an expert requirements-elicitation analyst that turns your vague idea into a clear, feasible spec: it clarifies the vague through investigation, reflects your idea back organized, offers better views, and reports what's closed-loop vs not. Investigation IS research: it reads the material you point at, searches its own knowledge, the web, the project's own data, skills and MCP, reasons it through, and runs probes to verify load-bearing truths — then drives every decision to closure and writes one authoritative, feasible SPEC.md. It resolves everything it can on its own and registers the reasoning; it asks you only about genuine forks that evidence can't settle, or when it found a better option than the one you proposed. Use /spec to define, refine, reconcile, or lock down what a project should be — before construction.

/yolo — the autonomous construct-to-green loop on top of /build (Gate 1.5). It schedules a recurring loop (Claude Code's /loop → CronCreate when available; otherwise an inline cycle) that keeps running /build in autonomous-to-green mode, code-reviews each round's diff, fixes the verified findings, and TERMINATES ITSELF (CronDelete) when no buildable work remains — or stops early and hands back to the human when it hits a genuine fork, a spec conflict, or two ticks with no progress. It changes /build's PACE, never its RULES: SPEC.md stays authoritative, done = acceptance + green gates, conflicts still route to /spec. Use /yolo when you've reviewed the spec, trust the gates, and want construction to just run to green without babysitting each checkpoint.