Skip to content

Commands Reference

Slash commands available in this project (universal + provisioned registry). For a tooling project these are the command-line / API surface.

47 commands — generated from source frontmatter.

Name Origin Description
auto-loop registry DEPRECATED — use /warp-drive instead.
autonomous-pm registry Autonomous PM front-end — from a vision doc alone, drive /business-case → /capability → /requirement → /groom to manufacture an approved queue warp-drive can consume, emitting human-only blockers as TODOs.
backlog registry Backlog Management
business-case universal Produce a business case (problem, options, cost/benefit, risk, recommendation, success metrics) as a GitHub Issue that sits above capability — the upstream justification lens.
capability universal Create a product capability (epic/spec) as a GitHub Issue.
cdfork registry Spawn parallel /warp-drive sessions in isolated git worktrees + tmux windows.
change registry Change Management
dashboard registry Project Dashboard
deploy registry Deploy via the resolved deploy adapter (cloudflare/node/drupal), parameterized by –env
design-brief registry Elicit and assemble a structured design brief for a feature or product surface, written as a project file artifact and printed to the terminal.
dev-up universal Bring dev environment to fully testable state (server, seed data, test users)
doc-bootstrap registry Bootstrap complete, tier-scaled, code-grounded documentation onto an existing (brownfield) project — triage → reconcile → generate → review → write → audit-clean
finish-work universal Merge current branch to main branch and cleanup
flightplan universal Derive an ordered warp-drive run plan ONCE and persist it as an issue-backed flight plan (label flight-plan).
groom universal Deep cap/req cluster reconciliation + warp-drive prep, plus business-case→vision fold-in (GitHub Issues)
incident registry Incident Management (GitHub Issues)
journal universal Create a new journal entry as a GitHub Issue
pr universal Create and manage pull requests with requirement traceability
provision universal Manage project provisioning (skills, commands, agents from registry)
rebob universal Rebob — Full Project State Reconciliation
release registry Create a versioned release with git tag and GitHub release
report-bug universal Bug Tracking
requirement registry Create or manage requirements as GitHub Issues (label req).
requirement universal Create a requirement as a GitHub Issue with acceptance criteria, priority, and labels.
research registry Manage research projects (questions, sources, findings, analysis, decisions)
retrospective registry Retrospective
review-lessons registry Surface unactioned lessons with tooling potential, grouped by theme
review-team registry Launch a four-role adversarial review team (implementer / tester / reviewer / lead) on Claude Code’s native Agent Teams feature, so no single agent both writes and approves its own code.
risk registry Risk Management
session-summary universal Create a summary of the current work session as a GitHub Issue
setup-promotion registry Scaffold a project’s dev→test→prod promotion ladder from its detected stack — one command, one review, stopping cleanly at the human gates
solution registry Propose or compare solution approaches as decision-labeled GitHub Issues
standup registry Daily Standup
start-work universal Start a new feature, fix, or other branch
status registry Status report — a thin alias of /what-next –report (on-demand catch-up + data-derived health + ranked next work)
swarm registry Run the full agent-swarm loop as one command — decompose, approve, dispatch in capped waves via cdfork, gate each result, integrate, and summarize.
threat-model registry Produce a structured threat model for a capability or feature BEFORE build — assets, trust boundaries, entry points, threats (STRIDE), and mitigations — recorded as a GitHub Issue so mitigations become trackable requirements.
trace-mining registry Mine past session journals and the structured decision log for failure patterns and distilled user preferences — the outer improvement loop for harness engineering.
update-journey registry Refresh the workday scenarios page (docs/explanation/workday-scenarios.md) from git history — restamp its inventory counts and date, and surface genuinely new commands/skills/agents for inclusion in the narrative.
update-story registry Refresh the project story page (story/index.html) from git history — restamp counts and date, and narrate genuinely new milestones into the timeline.
use-case universal Capture a use case as a persisted GitHub Issue, then decompose it into a capability (broad) or requirement(s) (narrow) — each realizing issue links back via “Realizes #NN”.
ux-review registry Create and manage UX reviews as GitHub Issues
versioning registry Provision and manage automated semantic versioning (commit-and-tag-version) for the current project
vision universal Create or update a project’s product vision & strategy document.
warp-drive universal Run the autonomous development loop — orchestrates work discovery, coding, documentation, commits, and merge/PR.
what-next universal Analyze project state and identify the next logical work item.
where universal Given a free-text task, return a ranked “start here” file map for the current repo — the ~5 files to open instead of reading the whole tree.