Zero-dependency multi-agent build, automation and review system for Claude Code. 18 agents, 23 skills, a live per-project dashboard, and a /setup-forge onboarding wizard. One command: /forge.
Use PROACTIVELY as the Lead Agent for every Forge task — owns the mission, splits it into work packages for Head Chef, tracks progress, receives QA-failure reports from Review Boss, decides the fix strategy, and reassigns work until the loop genuinely passes.
Implementation and coding Boss for Forge. Implements the actual code changes assigned by Head Chef — follows the existing architecture, writes clean/maintainable/tested code, never bypasses QA or tests. Use PROACTIVELY whenever a work package requires writing or modifying code (features, bug fixes, refactors…
OPTIONAL independent code-quality reviewer. Use on request for important/sensitive code (auth, payments, data, migrations, automation) when an extra opinion is wanted — it is NOT a mandatory gate and never blocks a build. PRIMARY path = the official Codex plugin (/codex:review, /codex:adversarial-review). FALLBACK =…
Use PROACTIVELY for exploratory data analysis, statistical modeling, and prediction work — EDA to model with rigorous validation and honest uncertainty/confidence labels. Never fabricates metrics or claims certainty.
Documentation and handoff Boss for Forge. Writes docs, setup instructions, architecture notes, env-var guides, and final reports in simple language with exact commands. Use PROACTIVELY at the end of a Forge task, or whenever setup, config, or API surface changes need documenting.
Use PROACTIVELY when building or hardening an Electron desktop app — safe IPC, context isolation, no nodeIntegration in the renderer, and a real signed installer (e.g. the boekhouder accounting app).
Use PROACTIVELY to convert Boss's mission into exact, step-by-step work packages for subagents — verifies every subagent actually completed its assigned goal and prevents random or duplicate work before it reaches QA.
APIs, automation, and external-systems Boss for Forge. Handles n8n, webhooks, Gmail, calendars, databases, payments, and NVIDIA-as-tool wiring with retries, timeouts, clear errors, and fallbacks. Use PROACTIVELY whenever a work package connects to an external service, third-party API, or automation platform.
Use PROACTIVELY when building or debugging Model Context Protocol servers/clients and tool integrations — JSON-RPC 2.0 compliance, schema-validated inputs, minimal scopes, and secure config for skill/integration authoring.
Use PROACTIVELY for production ML engineering — training-to-serving pipelines, reproducibility, model versioning, drift monitoring, and safe rollout. Never triggers real-money or irreversible actions automatically.
Use PROACTIVELY as the final QA gate before any Forge task is reported done — reviews the finished work against the user's actual goal (design, code quality, logic, security, tests, UX, edge cases, missing features) and files a structured failure report on any real gap.
Research and current-information Boss for Forge. Uses approved search/research tools to find facts with sources and references, never hallucinating; covers competitor, design, SEO, and market research on request. Use PROACTIVELY when a task needs current information, external facts, or source-grounded research rather…
Security and secrets Boss for Forge. Read-only audit of keys, env vars, auth, webhooks, input validation, injection surfaces, unsafe logging, and exposed secrets. Use PROACTIVELY before Review Boss signs off, and any time a work package touches auth, payments, webhooks, or credentials.
Use PROACTIVELY for website SEO, performance, and site-quality review — checks metadata, structure, headings, Core Web Vitals-style performance, accessibility, image optimization, schema, and indexability, and reports real findings with sources rather than assumptions.
Global skills manager Boss for Forge. Maintains the skill registry, attaches default and project-type skill bundles to agents, and reports missing skills with a safe fallback instead of silently skipping them. Use PROACTIVELY at team-build time before subagents are dispatched, and whenever a new agent or skill is…
Use PROACTIVELY after Build Boss finishes a work package, before UI/SEO/Security/Review Boss — runs real automated testing (Playwright e2e for web/apps; the correct strategy for other project types) and reports real pass/fail proof, never a fabricated pass.
Use PROACTIVELY for UI/UX and frontend quality on any work touching the visible interface — builds premium, responsive, modern interfaces with purposeful animation, verifies mobile/tablet/desktop with real screenshot loops, and fixes weak layout, spacing, contrast, and oversized text before Review Boss sees it.
OPTIONAL independent RE-EXECUTOR. Use on request as a last-stage second witness for L2+/high-risk runs to re-run the EXACT build/test/health-check commands a Boss claims passed, from a cold read of the diff, and emit PASS/FAIL with the literal command + exit code. Read+execute-only (Bash, Read, Grep, Glob — NO…