ratchet

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. Key insight: Progress is permanent. You can't un-ratchet. Given /ratchet [command] : Or check the chain manually: Steps: research , plan , implement , vibe , post-mortem Or record manually by writing to chain: Progress stored in .agents/ao/chain.jsonl : User says: /ratchet status What happens: Result: Single-screen view of RPI workflow progress, showing which gates passed and what's next. Skill says: After /research completes What happens: Result: Progress permanently recorded, gate locked, workflow advances without backsliding. - Progress is permanent - can't un-ratchet - Gates must pass - validate before proceeding - Record everything - maintain the chain - Skip explicitly - document why if skipping a step - Agent calls ao ratchet status 2>/dev/null to check current state - CLI reads .agents/ao/chain.jsonl and parses progress - Agent reports which steps are completed, in-progress, or pending - Agent shows output artifact paths for completed steps - Agent identifies next gate to pass - Agent calls ao ratchet record research --output ".agents/research/auth.md" - CLI appends completion entry to .agents/ao/chain.jsonl - Agent locks research step as permanently...