Graph Foreman — Productivity skill for Claude Code
Task-graph orchestration skill for Claude Code — parallel executors, enforced reviewer gate, live dashboard.
How to install Graph Foreman
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open JrSantiaggo/graph-foreman and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Graph Foreman does
Task-graph orchestration skill for Claude Code — parallel executors, enforced reviewer gate, live dashboard.
Alternatives in Productivity
- Parallel Task — Parallel Task Executor 1k ★
- Pi Subagents — Claude Code like Sub-Agents & Workflow Orchestration for Pi — parallel execution, live widget, fleet view, cus 967 ★
- Agentacct — See what your coding agents did and what it cost 665 ★
README
graph-foreman
**A foreman for your task graph**: executes an approved plan as a DAG — dispatching parallel subagent executors, refusing to sign off any task a fresh reviewer has not inspected, and watching the whole site on a live dashboard.
An agent skill for [Claude Code](https://claude.com/claude-code) and compatible agents, installable via [skills.sh](https://skills.sh/):
npx skills add JrSantiaggo/graph-foreman

What it does
- Parallel executors, capped — independent tasks run at once; up to 3 executors out of 4 total slots, so a finished task never waits for capacity to be reviewed.
- Author ≠ verifier, enforced — every task is validated by a FRESH reviewer agent that
never saw the code being written.
donerefuses a self-reported validation;reviewrefuses the task's own author. Evidence is recorded per verdict. - Collision-proof plans —
initrejects dependency cycles (naming the loop) and two parallel tasks that declare overlappingtouchespaths, before any agent starts. - Live dashboard — a read-only server on
:4949renders the DAG as phase swimlanes with animated dep edges, per-task state, retries and an event log. Killing it never affects a run. - Zero dependencies — three files, Node 18+, no npm install. State is plain JSON +
append-only NDJSON under
.specs/graph/(gitignored scratch). - Tokens are spent only by agents — the engine and the dashboard are plain Node processes making no model calls. Executors and reviewers (subagents) are the cost; the orchestrator adds a small constant overhead; watching the dashboard costs nothing.
What you need before running it
The skill executes, it never plans:
- An approved plan in the engine's format (
.specs/graph/plans/.plan.json— tasks, deps, vali
Related Skills
Axiom Planning
TDD-validated implementation planning with a four-reviewer plan-review quality gate - atomic-task plans with e
Jidoka Plan
Compose the orchestration graph for a task and open a resumable run-journal
Flowpane
FlowPane — a live graph of a Claude Code workflow run, drawn in the pane beside the transcript
Cezar
Cezar is a parallel coding agents orchestrator. Type a task, pick a workflow and an agent — Claude Code, Codex
Coducktor
Coducktor is a parallel coding agents orchestrator. Type a task, pick a workflow and an agent — Claude Code, C
Relay
Never lose your Claude Code context. Auto-handoff daemon with TUI, web dashboard, and multi-task orchestration
Related Agents
George
Factory floor foreman with four modes. (1) Status Report — runs the factory dashboard, interprets metrics, and
Graph Reader
Builds and queries a lightweight symbol/dependency graph of a project. Called by executors before reading file
Cto Parallel Work
CTO-grade parallel work orchestration. Designs task decomposition for concurrent agent execution, identifies f