ilkemerol/foreman

README preview

<h1 align="center">foreman</h1>
<p align="center">
  <img alt="Claude Code plugin" src="https://img.shields.io/badge/Claude%20Code-plugin-d97757?style=flat-square" />
  <img alt="bash + jq" src="https://img.shields.io/badge/needs-bash%20%2B%20jq-555?style=flat-square" />
</p>

<h3 align="center">The foreman plans. The crew builds.</h3>

<p align="center">
  <img alt="foreman - pixel-art night building site: the foreman holds the plan and sends orders to a crew of pixel agents on the floors, each showing its board stage" src="assets/foreman.svg" width="100%" />
</p>

## 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 <task>`.

View full repository on GitHub →