The Vision
What if your project board could execute itself? FORGE + TOMMY is a two-workflow orchestration system that turns GitHub issue hierarchies into completed code — autonomously. No copy-pasting prompts. No SSH sessions. No manual issue management. Point it at an epic, and it resolves the next unblocked ticket end-to-end.How It Works
FORGE is the strategic planner. It reads your GitHub epic, parses the block and task hierarchy, resolves which block is unblocked and ready, fetches every task’s acceptance criteria and file targets, and assembles a fully self-contained implementation prompt. Three execution modes: review it yourself (manual), let Claude handle it (api), or hand it to the robot (tommy). TOMMY is the tactical executor. When FORGE delegates via tommy mode, TOMMY receives the tasks, atomises them into individual task-lets, SSHes into your build server, and runsclaude --print --output-format json --max-turns 3 per task-let. On success, FORGE auto-closes the task and block issues with summary comments.
Zero-Token Orchestration
When FORGE delegates to TOMMY (Path C), the orchestration layer uses zero LLM tokens for planning. FORGE already did the thinking — TOMMY is pure mechanical execution. The only LLM calls happen inside Claude Code CLI on the build server, where they’re doing actual code generation.The Autonomy Ladder
| Level | Mode | Human Role | Status |
|---|---|---|---|
| 1 | Manual | Copy-paste prompt into Claude | Live |
| 2 | API | Review results after execution | Live |
| 3 | Tommy | Monitor; intervene on failure | Live |
| 4 | ZOID Councils | Approve at gates via Discord emoji | Planned |
| 5 | Full Autonomy | Sleep while it ships | Future |
What This Means
Point it at any GitHub org/repo with the right epic structure and it grinds through tasks overnight. Wake up to closed issues, committed code, and a board that moved itself forward.Current State
Successfully tested end-to-end ontraceo-ai/traceo-mcp-server epic #22. FORGE scanned 22 blocks, identified “BLOCK 5: Deployment & Go-Live” as the next unblocked ticket, assembled a 5,239-character prompt with full task context, and the workflow completed in under 60 seconds.