GitHub Repo
DryforgeJust explain it.
It builds the rest.
Your agent works like a senior developer.
/plugin marketplace add prekuter/dryforge /plugin install dryforge
Most harnesses box the agent in.
Dryforge bounds it.
Over-specify and the model works for the process. Under-specify and it chases a wrong read of the goal. Dryforge does neither.
Boxed in
Gate every step and the harness becomes the thing being scored. The model clears the checklist; whether that was the point comes second.
Bounded
Fix only what has to hold — approved intent, the order work depends on, what counts as proof — then leave the reasoning open.
Set the floor, not the ceiling. A sharper model makes a floor pay off; it only presses harder against a ceiling.
It replaces the stack.
It doesn’t sit on top of it.
The setup people build around a coding agent is a pile of separate parts. Dryforge is one design that does the same job — and the parts fit because they were never separate.
wired together, and kept in sync, by you
One design. Planning already knows what execution will do — they’re the same system. Nothing to glue, nothing to keep in sync.
Two commands. That’s the whole loop.
No mode to switch into, no interview to sit through. Run one, then the other, and read what comes back.
/ready — turn an idea into a plan you approve
It asks the decisions a senior dev asks first.
- what to build
- you decide — behavior, edge cases, the rules
- how to build
- the agent works out, unless a choice changes the result
- already in code
- it doesn’t re-ask what it can read
A wrong assumption caught at review means the question failed — not the review.
/go — build it, and prove it ran
Effort scales with risk: a rename runs straight through, a migration gets isolated and checked hard. Piling on tests and parallelism buys a little quality, and not for long. “Done” isn’t proof — a command that ran is.
/migration — for the code you already have
It reads the codebase and the old docs, then asks where a wrong guess gets expensive. Out comes the same doc set, and from there it’s /ready → /go.
Every run leaves a project harness behind.
The docs your agent opens first — committed to your repo as plain Markdown, yours to keep. Remove the plugin and the harness stays.
FAQ
When does it run?
Only when you type /ready, /go, or /migration. It stays out of the way otherwise.
Does it change my setup?
No. It's a plugin for Claude Code or Codex — no server, no account. Everything stays in the repo you already have.
Do I have to use it for everything?
No. Quick, obvious changes don't need it. It's worth it when getting the call wrong is expensive.
What does it need?
git. That's the whole list.
Tell /ready what you want built.
Install it, write one line, and let it take the first pass.
/plugin marketplace add prekuter/dryforge /plugin install dryforge