Installation
SpecForge installs in one line as a Claude Code plugin, and its skills also install into any skills.sh-compatible agent. Pick the path that fits you.
Prerequisites
Section titled “Prerequisites”- Claude Code — latest version. If you don’t see
the
/plugincommand, update Claude Code first. - git — for the marketplace source.
- Node.js (optional) — only for the skills.sh path (
npx).
Option 1 — Claude Code plugin (recommended)
Section titled “Option 1 — Claude Code plugin (recommended)”The full experience: commands + skills + subagents + the enforced gate.
/plugin marketplace add pooyagolchian/specforge/plugin install specforge@specforge/reload-pluginsNon-interactive / scripted:
claude plugin marketplace add pooyagolchian/specforgeclaude plugin install specforge@specforgeOption 2 — skills.sh (any agent, skills only)
Section titled “Option 2 — skills.sh (any agent, skills only)”Installs the lifecycle skills into 70+ agents.
npx skills add pooyagolchian/specforge # all skillsnpx skills add pooyagolchian/specforge --list # preview firstOption 3 — From source (try before you install / develop)
Section titled “Option 3 — From source (try before you install / develop)”git clone https://github.com/pooyagolchian/specforgeclaude --plugin-dir ./specforge/plugins/specforge--plugin-dir also accepts a .zip, and a local copy overrides an installed same-named plugin for
that session — handy while developing.
Option 4 — Team provisioning
Section titled “Option 4 — Team provisioning”Commit this to your repo’s .claude/settings.json so trusting teammates are auto-prompted to install:
{ "extraKnownMarketplaces": { "specforge": { "source": { "source": "github", "repo": "pooyagolchian/specforge" } } }, "enabledPlugins": { "specforge@specforge": true }}First run — and see the gate work
Section titled “First run — and see the gate work”/specforge:initFill in specforge/inputs/vision.md and tech-environment.md, then watch the gate enforce
spec-before-code:
| Step | What happens |
|---|---|
| Ask Claude to edit a source file now | 🚫 Blocked — no approved spec/plan |
/specforge:specify "…" → /specforge:plan |
drafts the spec + plan |
/specforge:approve specify && /specforge:approve plan |
✅ gate opens |
| Ask Claude to edit again | allowed — building under the plan |
/specforge:quick |
fast-track a trivial change (audited) |
Updating & uninstalling
Section titled “Updating & uninstalling”/plugin marketplace update # pull the latest/plugin uninstall specforge@specforge # remove the plugin/plugin marketplace remove specforge # optional: forget the marketplaceTroubleshooting
Section titled “Troubleshooting”| Symptom | Fix |
|---|---|
No /plugin command |
Update Claude Code to the latest version |
| Commands don’t appear | Run /reload-plugins |
| The gate never blocks | It’s inert without a specforge/ workspace — run /specforge:init; and the gate ships only with the plugin, not the skills.sh install |
| The gate blocks after approval | In specforge/state.md, the active feature’s specify and plan rows must read approved |
| Private/enterprise repo can’t clone | Configure a git credential helper for the marketplace source |
At a glance
Section titled “At a glance”| Method | Command | Gets the gate? | Best for |
|---|---|---|---|
| Plugin marketplace | /plugin install specforge@specforge |
✅ | Everyone (recommended) |
| skills.sh | npx skills add pooyagolchian/specforge |
❌ (skills) | Non-Claude-Code agents |
| From source | claude --plugin-dir … |
✅ | Trying it / development |
| Team settings | extraKnownMarketplaces + enabledPlugins |
✅ | Auto-provisioning a team |