Cheat Sheet
Print the agentic factory slash-command reference card.
Claude CodeGeneric
---
description: Print the agentic factory slash-command reference card.
---
Display the following cheat sheet **verbatim** to the user, then stop. Do not add commentary, do not run any other tool, do not invoke any other command.
---
# Agentic Software Factory — Cheat Sheet
Pipeline: **Discover → Define → Spec → Assemble → Run**, with adversarial gates between phases. Personas are subagents in `.claude/agents/` (dispatched via the Agent tool); specs live in `.specs/`.
| Command | Phase | Persona | Use case | One-liner |
| ---------------------------------------- | ------------------------------- | --------------------------- | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `/discover <signal>` | Discover (+ orchestrator) | `@Analyst` then main thread | New idea, raw feedback, bug report, transcript | Cluster the signal into `.specs/_intake/<slug>.md`, then auto-chain through `/challenge` → `/spec` → **spec approval gate** → `/plan` → `/challenge-plan` → `/build` → `/review` for every PBI. Halts on objections, the spec approval gate, or before `/ship`. |
| `/challenge <intake>` | Define gate | `@Critic` | Before writing any spec | Adversarially attack the problem statement. Returns `PASS` or numbered objections. |
| `/spec create\|reverse\|update <domain>` | Spec | `@Lead` | Write/refresh a living spec | Produces `.specs/<domain>/spec.md` with Blueprint + Contract + Gherkin. |
| `/plan <domain>` | Spec → Assemble | `@Lead` | Break the spec into work units | Writes atomic, isolated, self-testable PBIs to `.specs/<domain>/pbi/`. |
| `/challenge-plan <domain>` | Plan gate | `@Critic` | Before writing any code | Adversarially attack the PBI set (atomicity, isolation, self-testability, coverage). Returns `PASS` or numbered objections. |
| `/build <pbi-id> [--no-review]` | Assemble + Assemble gate | `@Dev` then `@Critic` | Implement and review one PBI | Phase 1: in-session Ralph Loop (edits + `lint` + `tsc` + `test:run`, max 10 iterations, micro-commits). Phase 2: dispatch fresh `@Critic` against the resulting diff. On Critic violations or `SPEC AMBIGUOUS`, stops and reports — no auto-loop. `--no-review` skips Phase 2 for trivial scaffolding PBIs. |
| `/review <pbi-id>` | Assemble gate | `@Critic` | Standalone adversarial code review | Same Critic pass that `/build` runs in Phase 2, available à la carte. Fresh `critic` subagent reads spec + Constitution + diff. Returns `PASS`, violations (tagged `[Spec]` or `[Constitution]`), or `SPEC AMBIGUOUS`. Use when you want to re-review a prior diff or when `/build` was run with `--no-review`. |
| `/ship <pbi-id>` | Acceptance | human (main thread) | Open the PR | Deterministic preflight (diff scope, cross-widget imports, `lib/` growth, gate-bypass markers) + strategic-fit checklist; awaits human approval, then pushes + opens PR. Self-service when preflight is green. |
| `/status <domain>` | — | main thread (read-only) | "Where am I?" diagnostic | Reads `.specs/<domain>/` and git history; prints which artifacts exist, which PBIs are built / reviewed / shipped, and the next suggested step. Never edits anything. |
| `/triage <signal>` | Run → Discover (+ orchestrator) | `@Analyst` then main thread | Production bug, metric, incident | Routes signal to spec amendment, regression guardrail, or new intake. On "new intake" auto-chains through the rest of the pipeline like `/discover`. |
| `/retro <domain>` | Agent Optimization Loop | `@Analyst` | After `/ship` or a stalled `/build` | Distills the completed pipeline into proposed amendments to the Constitution, AGENTS.md, personas, and templates. Produces diffs at `.specs/<domain>/retro.md`; does not apply them. |
| `/cheat-sheet` | — | — | This card | Prints this reference.
Maintain Cheat Sheet?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[Cheat Sheet on getagentictools](https://getagentictools.com/loops/futurice-agentic-software-factory-cheat-sheet?ref=badge)