Menu
Brownian Ratchet progress gates for RPI workflow. Check, record, verify. Triggers: "check gate", "verify progress", "ratchet status".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
This skill should be used when the user asks to "track issues", "create beads issue", "show blockers", "what's ready to work on", "beads routing", "prefix routing", "cross-rig beads", "BEADS_DIR", "two-level beads", "town vs rig beads", "slingable beads", or needs guidance on git-based issue tracking with the bd CLI.
Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".
Analyze code complexity and find refactor targets using radon/gocyclo. Triggers: "complexity", "analyze complexity", "find complex code", "refactor targets", "cyclomatic complexity", "code metrics".
Fully autonomous epic execution. Runs until ALL children are CLOSED. Level 1 uses /swarm (Task tool). Level 2 uses /spawn + Agent Mail for cross-session orchestration with Chiron help routing. NO human prompts, NO stopping.
This skill should be used when the user asks to "generate documentation", "validate docs", "check doc coverage", "find missing docs", "create code-map", "sync documentation", "update docs", or needs guidance on documentation generation and validation for any repository type. Triggers: doc, documentation, code-map, doc coverage, validate docs.
Extract decisions and learnings from Claude session transcripts. Triggers: "extract learnings", "process pending", SessionStart hook.
| name | ratchet |
| description | Brownian Ratchet progress gates for RPI workflow. Check, record, verify. Triggers: "check gate", "verify progress", "ratchet status". |
Track progress through the RPI workflow with permanent gates.
Note: /ratchet tracks and locks progress. It does not “run the loop” by itself—pair it with /crank (epic loop) or /swarm (Ralph loop) to actually execute work.
Progress = Chaos × Filter → Ratchet
| Phase | What Happens |
|---|---|
| Chaos | Multiple attempts (exploration, implementation) |
| Filter | Validation gates (tests, /vibe, review) |
| Ratchet | Lock progress permanently (merged, closed, stored) |
Key insight: Progress is permanent. You can't un-ratchet.
Given /ratchet [command]:
ao ratchet status 2>/dev/null
Or check the chain manually:
cat .agents/ao/chain.jsonl 2>/dev/null | tail -10
ao ratchet check <step> 2>/dev/null
Steps: research, plan, implement, vibe, post-mortem
ao ratchet record <step> --output "<artifact-path>" 2>/dev/null
Or record manually by writing to chain:
echo '{"step":"<step>","status":"completed","output":"<path>","time":"<ISO-timestamp>"}' >> .agents/ao/chain.jsonl
ao ratchet skip <step> --reason "<why>" 2>/dev/null
| Step | Gate | Output |
|---|---|---|
research | Research artifact exists | .agents/research/*.md |
plan | Plan artifact exists | .agents/plans/*.md |
implement | Code + tests pass | Source files |
vibe | /vibe passes | .agents/vibe/*.md |
post-mortem | Learnings extracted | .agents/retros/*.md |
Progress stored in .agents/ao/chain.jsonl:
{"step":"research","status":"completed","output":".agents/research/auth.md","time":"2026-01-25T10:00:00Z"}
{"step":"plan","status":"completed","output":".agents/plans/auth-plan.md","time":"2026-01-25T11:00:00Z"}
{"step":"implement","status":"in_progress","time":"2026-01-25T12:00:00Z"}