I tracked 18 days of my own Claude Code work on a client project:
- 46 hours at the desk, a prompt every 5.5 minutes
- 44% of that time was me reading and typing, not the model working
- 28 of 73 long turns ended with “X or Y next?” / “shall I commit?”, and I just said “go” Auto mode was already on, so permissions weren’t the issue. Claude could do the work, it just kept handing control back. Rules in CLAUDE.md helped for a while, then drifted. Foreman is a Claude Code plugin that turns those rules into hooks:
- Stop gate: during a run, Claude can’t stop until the project check passes, the plan has moved, and a Haiku judge agrees the stop is real (done, blocked on you, or a decision only you can make)
- Unit gate: runs the check before each next subagent starts
- /foreman:init proves each check can actually fail (it found my
make checkwasn’t running the frontend tests) - Per-unit commits, a decisions log, and a hand-back report instead of a chat history
- New in 0.4.0, /foreman:review: reviews a finished run from its transcripts, locally. You get a private write-up of why it went the way it did, plus a redacted issue draft (commands reduced to shapes, names and secrets stripped) you can read and post if Foreman misbehaved
Install:
claude plugin marketplace add michalzan/foreman
claude plugin install foreman@michalzan
Honest caveats: nine runs, one person, no control group. It runs locally with no sandbox, so read the “What it does not protect” section before leaving it alone.
Repo:
https://github.com/michalzan/foreman
If you try it,
/foreman:reviewafter a run is the most useful feedback you can send me. Also keen to hear if you think the approach is wrong. submitted by /u/belovoj
Originally posted by u/belovoj on r/ClaudeCode
You must log in or # to comment.