Turn Claude Code into a structured, multi-agent development team that never skips the spec.
Pick whichever channel fits your workflow.
A — curl | sh (no Node required)
curl -fsSL https://raw.githubusercontent.com/bfontaine/forge/main/bin/forge-install.sh | bashB — @sdd-forge/cli (npm)
npx @sdd-forge/cli init
# or install globally
npm install -g @sdd-forge/cli && forge initC — Docker (CI)
docker run --rm -v "$PWD:/workspace" -w /workspace forge/linter:latestThen, open Claude Code in the project directory and run /forge. It
auto-detects state and routes you to the right phase.
Installation guarantees (shared by A and B):
- Idempotent — re-runs never clobber your edits without
--force. .forge/product/*is always scaffolded from templates, so your mission and roadmap are yours, not Forge's.- Private Claude Code state (
.claude/settings.local.json) is never copied.
| Command | Description |
|---|---|
/forge |
Master command — auto-detects state and routes |
/forge:init |
Initialize Forge (new or existing project) |
/forge:discover |
Extract existing conventions as standards |
/forge:vision |
Define product mission and value proposition |
/forge:new <name> |
Start a new feature (propose + specify) |
/forge:propose <name> |
Create a change proposal |
/forge:specify <name> |
Write delta specifications |
/forge:design <name> |
Create technical design |
/forge:plan <name> |
Generate TDD-ordered task list |
/forge:implement <name> |
Execute next task (TDD cycle) |
/forge:review <name> |
Run quality gates |
/forge:archive <name> |
Merge specs and mark complete |
/forge:explore |
Free brainstorm / research |
/forge:verify <name> |
Verify spec-to-code alignment (3 dimensions) |
/forge:clarify <name> |
Identify spec ambiguities before design |
/forge:diff <name> |
Semantic spec diff (ADDED/MODIFIED/REMOVED) |
/forge:metrics |
Development velocity metrics and bottleneck analysis |
/forge:onboard |
New contributor orientation and checklist |
/forge:status |
Full project state report |
| Agent | Name | Specialty |
|---|---|---|
| Flutter Orchestrator | Hera | Team coordination, feature workflow |
| Flutter Architect | Athena | Clean Architecture, FSD, DI |
| Flutter TDD-BDD | Spartan | Test enforcement, zero tolerance |
| Flutter UX/UI | Apollo | Multi-platform design, Material 3 |
| Flutter Widgets | Hephaestus | Custom widgets, animations |
| Flutter Performance | Hermes | Profiling, optimization |
| Flutter A11y & i18n | Iris | Accessibility, internationalization |
| Flutter OTel | Argus | Client-side instrumentation |
| Flutter AI | Prometheus | Voice, GenUI, agents |
| Flutter Quality | Nemesis | Final gate, delegation |
| Agent | Name | Specialty |
|---|---|---|
| Rust Orchestrator | Vulcan | Team coordination |
| Rust Architect | Ferris | Hexagonal architecture, gRPC |
| Rust TDD-BDD | Centurion | Test enforcement |
| Rust TUI | Terminal | ratatui, Elm architecture |
| Rust OTel | Sentinel | Server-side instrumentation |
| Rust Quality | Tribune | Final gate |
| Agent | Name | Specialty |
|---|---|---|
| Forge Master | Forge | Orchestration, routing |
| Spec Writer | Clio | Requirements, RFC 2119 |
| DDD Strategist | Socrates | Domain modeling, Event Storming |
| AI-First Brainstorm | Oracle | AI workshop, agent architecture |
| Infra Architect | Atlas | Docker, K8s, Kong, Temporal |
| Observability | Panoptes | OTel, SigNoz, ELK, Prometheus |
| Security Auditor | Aegis | Security audit, OWASP |
| DevOps Engineer | Heracles | CI/CD, deployment |
| Product Analyst | Pythia | PRFAQ, competitive analysis, product briefs |
| Technical Writer | Calliope | Changelogs, release notes, API docs |
| API Designer | Hermes-API | OpenAPI, AsyncAPI, gRPC contracts |
| Test Architect | Eris | Test pyramid, mutation testing, flaky detection |
Superpowers — TDD delegation is built in. When /forge:implement runs, it delegates to the appropriate TDD agent (
Spartan for Flutter, Centurion for Rust) who enforces the RED → GREEN → REFACTOR cycle without exception.
oh-my-claudecode — Forge responds to OMC keyword triggers:
autopilot→ full pipeline executionulw→ ultrawork mode (deep implementation)team→ explicit multi-agent delegation
Context7 — External API documentation is resolved automatically via the MCP server. Forge calls resolve-library-id
then query-docs to fetch up-to-date docs rather than relying on training data.
- Specs are the source code of intent — Code is ephemeral; specs are the durable record of what was decided and why.
- TDD is non-negotiable, not optional — Every task in every feature follows RED → GREEN → REFACTOR. No exceptions, no rationalization accepted.
- Quality is structural, not willpower-based — Quality gates, constitution checks, and delegation patterns make quality the path of least resistance.
Apache License 2.0. See LICENSE for the full terms and NOTICE for upstream attributions (BMAD Method, GitHub SpecKit, OpenSpec, Agent OS v3, Superpowers, oh-my-claudecode, Context7).
- Governance model — maintainers, decision making, amendment process, release process
- Contributor Covenant Code of Conduct
- Security policy — private disclosure channels
- Changelog — Keep a Changelog format
- Versioning policy — SemVer, coupled to the Constitution