Workflows to chain agents together.
Each project in your dev ecosystem has its own CLI and its own Claude Code agents. Forge connects them: you define a workflow as YAML steps, and forge spawns an agent team that executes them in order, routing data between projects.
- Claude Code CLI
Each workflow references projects from the registry. You only need the projects a given workflow calls — forge tells you which ones are missing.
git clone <repo-url> ~/dev/forge
cd ~/dev/forge
The /forge skill is available in any Claude Code session rooted in this
directory.
Forge
├─ reads workflow definitions (workflows/*.yaml)
├─ reads project interfaces (registry/*.yaml)
└─ spawns agent teams to execute steps
Projects expose CLI interfaces:
Reck ─── reck review, reck assess
Shipyard ─── fl drive, fl spawn, fl status, fl review
Blueprint ─── blueprint compile, blueprint enforce
Lore ─── lore.sh search, lore.sh learn, lore.sh context
Council ─── council advise (via agents)
Each project runs its own code. Forge defines the order, routes data between steps, and tracks outcomes.
/forge fleet-dispatch --task PMS-1234
/forge spec-synthesis --spec requirements.md
/forge list
| Directory | Purpose |
|---|---|
| registry/ | Project interface declarations (YAML) |
| workflows/ | Workflow definitions (YAML) |
| .claude/ | Skill and agent definitions |
| Workflow | Chain | Status |
|---|---|---|
| fleet-dispatch | Shipyard → Reck → Lore | Draft |
| spec-synthesis | spec-trace → Shipyard → coalesce | Draft |
| spec-proposals | Lore → 3× proposals → Council → synthesize | Draft |
Draft — functional but not battle-tested. Interface may change.