@garygentry/feature-forge
Cross-agent installer for the feature-forge skill suite — installs the canonical forge pipeline into Claude, Codex, Copilot, Cursor, Gemini, or Pi.
Package details
Install @garygentry/feature-forge from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@garygentry/feature-forge- Package
@garygentry/feature-forge- Version
0.3.1- Published
- Jul 30, 2026
- Downloads
- 2,379/mo · 246/wk
- Author
- garygentry
- License
- MIT
- Types
- extension, skill
- Size
- 9.8 MB
- Dependencies
- 0 dependencies · 0 peers
Pi manifest JSON
{
"skills": [
"./adapters/pi/skills"
],
"extensions": [
"./adapters/pi/extensions/ask-user-question/index.ts"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
@garygentry/feature-forge
Cross-agent installer for the feature-forge skill suite — an end-to-end feature-development pipeline that runs on any coding agent (Claude, Codex, Copilot, Cursor, Gemini, or Pi).
This package installs the canonical forge skills into the agents detected on your machine. It is dependency-free and performs sandboxed, manifest-tracked writes.
Usage
# Install into every detected agent:
npx @garygentry/feature-forge install
# Scope to one agent:
npx @garygentry/feature-forge install -a codex
# Preview the plan without writing anything:
npx @garygentry/feature-forge install --dry-run --json
Commands
| Command | Description |
|---|---|
install (add) |
Install feature-forge into the target agent(s). |
update |
Reconcile an existing install to the current adapters. |
uninstall (remove) |
Remove a prior install (manifest-tracked files only). |
list (ls) |
Report per-agent detected / installed / up-to-date status. |
Common flags
| Flag | Description |
|---|---|
-a, --agent <id> |
Scope to one agent (claude/codex/copilot/cursor/gemini/pi). |
-g, --global |
Install into the user-level config dir (default: project-local). |
--symlink |
Symlink the bundle instead of copying (Windows always copies). |
--dry-run |
Print the planned actions without changing anything. |
--json |
Emit the run report as JSON. |
--skip-rauf |
Skip the rauf resolvability preflight (records raufPin: null). |
Per-agent install layout
Each agent's bundle is installed where that agent actually loads it (project scope shown;
--global resolves the same paths under ~):
| Agent | Primary bundle | Second-root placement |
|---|---|---|
| claude | .claude/skills/feature-forge/ |
— |
| codex | .agents/skills/feature-forge/ |
.codex/agents/*.toml (custom agents, mirrored flat) |
| copilot | .github/feature-forge/ |
managed block in .github/copilot-instructions.md |
| cursor | .cursor/rules/feature-forge/ |
— |
| gemini | .gemini/extensions/feature-forge/ |
— |
| pi | .pi/skills/feature-forge/ |
— |
For Pi, --global installs to ~/.pi/agent/skills/feature-forge/ and project scope installs to ./.pi/skills/feature-forge/. The Pi bundle includes real package.json metadata plus the AskUserQuestion compatibility extension; run /trust (or use --approve in non-interactive tests) before relying on project-local Pi resources.
The Copilot block is delimited by <!-- feature-forge:managed:start --> /
<!-- feature-forge:managed:end --> sentinels and merged without disturbing the rest of the
file. update refreshes it (a hand-edited block is left alone unless --force); uninstall
strips only the block, deleting the file only if nothing else remains.
Claude
Claude Code users can alternatively install via the plugin marketplace:
/plugin marketplace add garygentry/feature-forge
/plugin install feature-forge@feature-forge
Notes
The default loop runner is rauf, published as
@garygentry/rauf. The installer runs a
read-only resolvability preflight on the pin (@garygentry/rauf@0.13.0) and records it; pass
--skip-rauf to defer the check (e.g. offline installs). Install the rauf CLI itself with
npx @garygentry/rauf or its
binary script. See the
feature-forge README for the full
pipeline documentation and per-agent setup guides.
The installer never writes a forge.config.json — it deploys only the bundled skills and
runtime helpers. Configuration authorship belongs to /feature-forge:forge-init, which creates
the config and surfaces the auto-verify opt-in (whether to run forge-verify automatically after
each stage) at setup time.
License
MIT