Foreman

Foreman

A Boris-style agentic orchestrator TUI that supervises headless Claude Code agents through a _gated_ software-delivery pipeline — pointed at any repository.

plan → ADR/PRD → issues → TDD build → e2e

Why Foreman? · Demo · Quickstart · Guide · How it works · Roadmap · Contributing
_"I don't prompt Claude anymore; I have loops that prompt Claude."_

Foreman spawns the locally-installed claude CLI in headless stream-json mode,
parses its event stream, enforces budgets, and drives your delivery workflow with
a human-in-the-loop review gate for the design phases and guardrailed autonomy for
the build. All state is human-readable files committed inside the target repo —
no database; kill it and restart and it fully recovers from disk.

Table of contents

- Why Foreman?
- Demo
- 5-minute quickstart
- Guide — driving the TUI
- How it works
- Roadmap
- File layout
- Configuration
- The vendored skills
- Development
- Contributing
- FAQ
- Acknowledgements
- License

Why Foreman?

Running a coding agent in a while loop is easy. Running one you can trust to
merge is not. Foreman is the supervisor in between: it keeps a human at the design
gates, then hands the build to agents that are boxed in by the orchestrator, not
by their own good behaviour.

- 🚦 Gated pipeline — plan → ADR/PRD → issues → TDD build → e2e, with human review gates on every design phase and a hash-sealed approval that auto-reverts if a doc changes.
- 🤖 Real headless agents — spawns the locally-installed claude CLI in stream-json mode, parses its events, and enforces per-run turn/cost/time budgets.
- 💾 No database — all state is human-readable files committed inside the target repo. Crash-safe: kill it mid-build and it recovers from disk.
- ⌨️ Keyboard-driven TUI — drive the entire workflow from a…