Zero-ratchet dropped on GitHub yesterday. It’s a structured workflow for AI coding agents. And the part worth paying attention to isn’t the stages. It’s who does the reviewing.
Here’s the twist: most agent setups let the same model that wrote the code also review it. That’s like asking someone to grade their own exam. Zero-ratchet solves this by bringing in fresh-context reviewers at every checkpoint. A separate context window. A genuinely independent read.
How the workflow runs:
- 🧠 Product flow: idea → discovery → PRD → roadmap → UI brief
- 📋 Engineering flow: design → story plan → TDD loop → review → traceability → PR
- 🔒 Gates: explicit checkpoints between every stage. Nothing moves forward until it passes.
- 👁️ Fresh reviewers: new context window at review time. The agent that built it doesn’t sign off on it.
Host-agnostic setup, so it works with Claude Code, Cursor, Hermes, or anything that loads skills from a directory.
Pro tip: The author is upfront that this is overkill for small one-shot changes. But for semi-unattended agents working across multiple artifacts (PRDs, stories, test suites, PRs), staged gates are the difference between “it probably worked” and actually knowing it worked.
Pro tip 2: The product flow stage forces discovery before any code gets written. Most pipelines skip straight to implementation. Slowing down here actually speeds things up later.
Worth a look if you’re experimenting with longer-horizon agent work. 🚀 Grab it at github.com/zero-click/zero-ratchet.
Frequently Asked Questions
Q: Does zero-ratchet force AI to think about constraints and interdependencies, not just high-level task lists?
Yes. The discovery, PRD, and roadmap stages include explicit gates for identifying constraints, edge cases, and how design decisions ripple through the project. Rather than jumping straight to “do 1, 2, 3, 4,” the workflow forces the AI to understand the “why” and consider what impacts what, something commenters noted is often missing in AI-generated plans.
Q: How does zero-ratchet prevent shallow design reviews?
It uses fresh-context reviewers, independent agents that haven’t seen the original work and approach it with a critical eye. This avoids the trap of the original agent only grading its own homework, which typically misses the very issues it introduced.
Q: When should I use zero-ratchet vs. just prompting an AI directly?
For small, well-defined changes, direct prompting is faster. But for complex projects with many moving parts, zero-ratchet’s stage gates help catch design flaws early. It’s aimed at people doing longer-horizon or semi-unattended workflows where reliability matters more than speed.
Q: Can zero-ratchet explain how design choices impact different parts of a project?
The roadmap and story-plan stages require mapping dependencies and trade-offs explicitly. Rather than treating each task in isolation, the AI must show how decisions in one area (e.g., architecture) affect downstream areas (e.g., testing, deployment).
zero-ratchet: a gated workflow for AI coding agents
by u/skybeefu in PromptEngineering