The /dr-help Command — Datarim Command Reference
What /dr-help shows: the full pipeline, all command categories, the complexity routing table, the agent roster, and backlog navigation — in one place.
When the right next step is not obvious, /dr-help surfaces it. The command prints the complete Datarim command reference without touching any files or state. It is read-only and safe to run at any point in a task.
The pipeline and complexity routing
The reference starts with the standard pipeline: init → prd → plan → design → do → qa → compliance → archive. Not every task goes through every stage. The complexity table explains which stages apply at each level: an L1 quick fix follows init → do → archive; an L4 major feature follows the full sequence with phased execution. Stages shown in brackets are optional — included when the agent determines they add value for that specific task.
Research runs inside /dr-prd for L2 and above as Phase 1.3. Gap discovery runs inside /dr-do when the implementation encounters unknowns. Reflection runs automatically as mandatory Step 0.5 inside /dr-archive.
Command categories
Commands are grouped into four categories. Eight pipeline commands cover the task lifecycle from initialization through archiving. Two content commands — /dr-write and /dr-edit — handle articles, documentation, and posts through writer and editor agents. Three framework management commands — /dr-addskill, /dr-optimize, and /dr-dream — maintain the framework and knowledge base. Three utility commands cover status, resumption, and this reference itself.
Two standalone commands round out the list: /factcheck and /humanize for targeted, one-off checks outside the full editorial pipeline.
The agent roster
The reference lists all seventeen agents with their roles: planner, architect, researcher, developer, tester, reviewer, compliance, code-simplifier, strategist, devops, writer, editor, skill-creator, optimizer, librarian, security, and sre. Each agent has a defined scope and runs on a model matched to its workload. The agent table in /dr-help is the canonical reference for which agent runs at which stage — useful when diagnosing unexpected behavior or planning which commands a new task will pass through.
Backlog and project scaffolding
The reference also covers the two-file backlog system: datarim/backlog.md for active items and datarim/backlog-archive.md for completed ones. It documents the /dr-init create project syntax that scaffolds a full project structure — CLAUDE.md, docs directories, datarim state, and archive folders — detecting the tech stack from the project description. The scaffolding is idempotent: running it on an existing project skips what already exists.
For the bigger picture of what Datarim does and why, start with what Datarim is. For keeping the framework trim as it grows, see /dr-optimize.