build-loopExecute Do-it tasks. Reads .do-it/specs/ (current truth) and .do-it/changes/ (proposals), picks the next buildable band, builds under TDD discipline (software) or acceptance-driven (generic), respects the UI-first layer gate, and keeps the loop memo current. Product review runs per feature; optional
designEmit the compact design state the build loop consumes: tokens, the F0 foundation manifest, and per-entity contracts. Narrative design docs defer to --full.
do-itRun the Do-it spec-driven MVP workflow in Codex. Use for PRD, brownfield mapping, config migration, grilling, design, preview, building, review, iteration, project status, retrospectives, or autonomous delivery.
grillAdversarially challenge a spec-layer artifact — PRD, change proposal, or design system — before code exists. Hunts gaps, contradictions, ambiguity, scope creep. Triggered by /do-it:grill or "challenge the PRD", "poke holes".
iterate-fixApply fixes after a REVISE verdict, or after a task's mechanical gate goes red. Root-cause discipline only — no symptom fixes, no test-softening. Triggered by /iterate, or by the Ralph loop on a red gate or a REVISE.
llm-wikiMaintain docs/ as an optional LLM Wiki. Direct Pass/Query always work; automatic passes run only when project knowledge maintenance enables them.
loop-runnerSet up and explain Do-it's autonomous drivers — /do-it:loop (Claude Code's native loop, deterministic stop via scripts/loop-guard.sh) and /do-it:ralph (the legacy in-session Stop hook that re-feeds the iteration contract). Preflight, settings resolution, the stop report, and stop semantics for both.
map-codebaseWalk an existing codebase with parallel mapper subagents into .do-it/codebase/ — 7 files: stack, integrations, architecture, structure, conventions, testing, concerns. Detects and migrates GSD, Superpowers, or Ralph Loop v0.1 state; optional wiki seeding follows knowledge maintenance. Run by /do-it:
prd-generatorUse when the user wants to start a new project from a PRD. Triggers include "create a PRD", "write product requirements", "build a product spec", "clone a product", "replicate a product", "generate a PRD for", or any /prd command in the Do-it plugin. Produces .do-it/specs/prd.md as the foundation do
retrospectMine progress, metrics, review findings and failed attempts into durable lessons. Direct runs always work; automatic archive runs require knowledge maintenance to be enabled.
review-workAdversarial review of a completed FEATURE (default) or a single task — spec compliance and quality+security as two fresh subagents in parallel, dispatched with the briefs in references/briefs/. Used by /do-it:review, and by build-loop before a change is archived.
statusRead-only briefing of the current Do-it project — features, current change, gates, live preview, spec coverage, recent activity, suggested next move. Run by /do-it:status. Never writes anything.
worktreesRun each open Do-it change in an isolated git worktree under .worktrees/. Substrate for parallel features — required whenever the loop fans out (subagent_concurrency > 1), also usable serially via _meta.json use_worktrees.