Foreman

foreman

The foreman plans. The crew builds.

What it is

One Claude Code session can do a lot on its own. But when a task has several independent pieces, doing them inline fills the main context with file dumps and test output, runs the pieces one after another, and leaves you trusting the session's own word that each one worked.

foreman is a Claude Code plugin that turns the main session into an orchestrator. Like a foreman on a building site, it reads the plan, splits the work, hands each piece to a crew member and checks the result - but it does not lay bricks itself. The main session plans, spawns subagents, relays between them and verifies what they return; the subagents do the work.

You turn it on with /foreman on for the whole session, or run a single task or skill through it with /foreman .

Features

- The main context stays clean - every change, even a one-liner, goes to a subagent; the main session keeps only the conclusions.
- Parallel pieces - pieces that do not depend on each other are spawned in one message, so they run at the same time; only a real dependency is serialized.
- Verified results - an agent's done is a claim, not proof. The foreman reads the diff or runs the check before accepting it, and reports what stays not verified.
- One level deep - only the main session spawns agents. Agents never spawn agents, never message each other, and report only to the foreman. A hook enforces it.
- A fitting agent per piece - locating, small edits, reviews, plans and multi-step work each go to a matching agent type, with a cheaper model and lower effort for mechanical pieces.
- Agent board - one table of every agent, its job and its stage (queued, running, waiting, verifying, done, failed), kept in step by hooks.
- Status line badge - [FOREMAN:ON],…