forge is a portable pipeline that installs into Claude Code. You describe the work as tickets; forge plans it, writes it, reviews it, gates it, and opens the PR. Every change ticketed, trailed, and auditable — not ad-hoc prompting.
Prompting gets you code. A pipeline gets you shipped software — reviewed, gated, and on the record.
Ad-hoc AI coding produces changes nobody planned, nothing reviewed, and no trail of why. forge replaces the improvisation with an opinionated delivery pipeline: the same plan → build → gate → review → merge loop for every change, whether you start a fresh project or adopt an existing one.
The board is the source of truth. Every lifecycle moment is written back to the driving issue — no silent side-work. If a gate says no, it's a script, not an opinion.
Each skill is a /forge:<skill> command that spawns the right roles with fresh context and hands off down the line.
Seven mechanical gates run as scripts at ship, not opinions — plus an adversarial reviewer and security pass over the whole diff, model-driven rather than mechanical. Fail-closed, every time.
Incident and security-response situations lock what's allowed — hotfix-only, or nothing ships.
Branch, commit, and PR naming follow the convention — no punctuation-only squashes.
The diff stays inside the plan's declared files and blast radius.
Tests assert real behaviour, not tautologies that pass on anything.
New dependencies are declared, justified, and inside policy.
Every acceptance-criteria id is proven by a passing test — no untested AC ships.
Docs and route index move in lockstep with the code they describe.
Adversarial passes · model-driven, not mechanical
A full-diff review subagent returns pass with zero critical or high findings.
An adversarial pass treats the diff as hostile: injection, secrets, supply chain.
The law: ticket-first, always — silent side-work is forbidden. The owner merges every PR; unattended auto-merge is Claude-only, by policy. “Unknown” is a valid answer.
forge spawns role subagents instead of one over-loaded prompt. Each has a role card, a narrow tool set, and a single responsibility.
forge is built by its own pipeline. Every commit here shipped through the same skills it installs.
Prerequisites: Claude Code, Node ≥ 22.13, pnpm 10.14+, and a GitHub account. Full wiring in the install guide. Running Antigravity instead? Same Node/git/gh, plus agy on PATH. There's no marketplace for agy, so it's three steps, not one: clone a forge checkout, emit into your project, commit what's emitted — see the box alongside.
/plugin marketplace add dngioidev/forge /plugin install forge@forge /forge:init
git clone https://github.com/dngioidev/forge C:\tools\forge cd C:\my\project node C:\tools\forge\plugin\scripts\init.mjs --host agy
Run the last line from your project's directory, with an absolute path to the checkout — the emitter resolves its output relative to cwd. Then commit the emitted .agents/plugins/forge/ (~126 files) — that's what every teammate shares, no checkout required on their side. (macOS/Linux: forward slashes, e.g. ~/tools/forge.)