Print the full command reference for the NestJS SDM kit. Use when you want to see all available commands, the CR process flow, or how to get started.
Print the following reference exactly as shown — no additions, no commentary:
Everything is a Change Request. One process, no exceptions.
/code-review (optional discovery)
↓
/intake → /cr <cr-id> ← automated pipeline (recommended)
or step by step:
/intake → /spec → /plan → /build → /close
Critical incident fast track:
/intake → /build → /close
| Command | Stage | What it does |
|---|---|---|
/init | Setup | One-time project setup. Creates specs/project.md, scaffolds folder structure. Run once before anything else. |
/intake | Intake | Universal entry point. Bring anything — problem, bug, finding, request, incident, URL, file. Classifies into 6 CR types, produces a CR item. |
/cr <cr-id> | Pipeline | Automated pipeline — routes by CR type. Stops only at mandatory human gates. |
/spec <cr-id> | Spec | Full or lean spec — 10 sections for features, 3 sections for changes/refactors. Multi-agent review. |
/plan <cr-id> | Plan | Implementation blueprint + TDD tests written before code. Human confirms approach. |
/build <cr-id> | Build | TDD: red → green per layer. Code review. Containment for Critical/Security. Direct fix for bugs. |
/close <cr-id> | Close | Verify ACs, update project map, document decisions, formal closure. |
/code-review | Discovery | Multi-agent audit of existing NestJS code. Produces findings report. |
/status | — | Shows all CRs: open, in progress, blocked, recently closed. No arguments. |
| Type | When to use | Track |
|---|---|---|
feature | New capability, new module, new endpoint | /intake → /spec (10 sections) → /plan → /build → /close |
bug | Existing behavior is broken | /intake → /build (locate → regression test → fix) → /close |
change | Small modification — config, limit, copy | /intake → /spec (3 sections) → /build → /close |
security | Auth gap, RLS breach, secrets, OIDC | /intake → /spec → /plan → /build → /close |
incident | Production down or data at risk | /intake → /build (contain first) → /close |
refactor | Internal restructure, no behavior change | /intake → /spec (3 sections) → /build → /close |
Auto-generated at intake: YYMMDD-HHMMSS — e.g. 260311-143022
/intake — plain text, file, URL, Jira ticket, error log, findings reportspecs/project.md ← Project memory (created by /init, updated by /close)
specs/cr/<cr-id>.cr.md ← CR item (created by /intake, updated through lifecycle)
specs/cr/<cr-id>.spec.md ← Spec (created by /spec — full or lean)
specs/cr/plans/<cr-id>.plan.md ← Plan (created by /plan — features only)
src/modules/<m>/ ← TDD tests written before code (created by /plan)
specs/reviews/<scope>-<date>.md ← Review report (created by /code-review)