[](https://4ge.sh)
[](https://www.npmjs.com/package/@entelligentsia/forgecli)
[](#)
[](#)
[](https://github.com/Entelligentsia/forge)
[](https://www.npmjs.com/package/@earendil-works/pi-coding-agent)
> **engineering software** — a coding harness for agents.
> Three aliases: `forge` · `forgecli` · `4ge`.
forge-cli generates a project-specific engineering knowledge base, sprint workflows, agent personas, and an SDLC pipeline — then drives them from your terminal on the [pi-coding-agent] runtime. Model-agnostic. No editor lock-in.
> **Two ways to run Forge.** Drive it headless in your terminal on the pi runtime (this README), **or** scaffold Forge into a Claude Code project with `4ge init claude .` and run the `/forge:*` slash commands inside Claude Code — remove it with `4ge uninstall claude`. The `4ge init` path is the supported way to add Forge to Claude Code and **replaces the deprecated marketplace plugin install** ([why](https://github.com/Entelligentsia/forge#distribution)).
## Why
- **Structured SDLC, in any terminal.** Plan → implement → review → validate → commit chains, gated by your own personas and audience rules.
- **Project memory that compounds.** Every sprint sharpens the knowledge base; the next one starts smarter.
- **Skills that stay relevant.** Forge ships a SkillOS-style curation loop (FORGE-S24). Five friction subkinds — `skill_unused`, `skill_failed`, `skill_missing`, `skill_stale`, `skill_redundant` — surface what the model actually reached for, what worked, and what didn't. Phase 2 enhancement classifies proposals as `insert_skill` / `update_skill` / `delete_skill`, scores them through an LLM-judge rubric, gates oversize edits behind a compression check, and drains a per-task curator queue into one batched review at sprint close. The result: your skill library tracks your codebase as it evolves, instead of calcifying.
- **Bring your own model.** Anthropic, OpenAI, ollama, openrouter — anything pi resolves.
## Install
```sh
curl -fsSL https://4ge.sh | sh
```
Or via npm directly:
```sh
npm install -g @entelligentsia/forgecli
```
Node 20 or higher. The curl installer checks prerequisites, runs the npm install, and verifies `forge` is on your PATH.
## Quick start
```sh
cd your-project
forge # launch (forge, forgecli, and 4ge are the same binary)
> /forge:init # generates KB, personas, workflows, commands
> /forge:new-sprint # start your first sprint
> /forge:plan-sprint # break requirements into tasks
> /forge:run-sprint S01 # execute — plan → review → implement → approve → commit
> /forge:retro S01 # close the sprint and feed learnings back
```
## Try it on the playground
Don't want to point forge-cli at your real codebase first? Clone the testbench and run a full SDLC cycle on a sample project in ~15 min:
```sh
git clone https://github.com/Entelligentsia/forge-testbench
cd forge-testbench/hello # smallest project — Python · Click · 21 lines
forge
> /forge:init
```
Three more stacks live in the testbench — TypeScript ([cartographer]), Go ([emberglow]), Python+NumPy ([spectral]). Walkthrough on the [testbench README](https://github.com/Entelligentsia/forge-testbench).
## What `/forge:init` does
```
① collect 5 parallel discovery scans → .forge/config.json
② discover KB docs + project-context → .forge/project-context.json
③ generate personas, workflows, commands → .forge/{personas,workflows,…}
④ register manifest + cache + store entries → .forge/store/, .forge/cache/
```
Idempotent and resumable. Re-running picks up at the last checkpoint via `.forge/init-progress.json`.
## Commands
```
SETUP /forge:init Bootstrap Forge SDLC into the project
/forge:rebuild Refresh generated workflows, KB, or tools
/forge:update Check for + apply forge-cli updates
/forge:add-pipeline Add or customize a pipeline interactively
/forge:remove Tear down the Forge install
RUN /forge:run-task Execute one task pipeline end-to-end
/forge:run-sprint Orchestrate every task in a sprint
/forge:fix-bug Triage + fix flow
/forge:new-sprint Elicit sprint requirements
/forge:plan-sprint Decompose a sprint into tasks
/forge:add-task Add a task to an existing sprint mid-flight
/forge:retro Produce a sprint retrospective document
CHAIN /forge:plan plan
/forge:implement implement
/forge:review-plan review the plan
/forge:review-code review the code
/forge:approve architect approval
/forge:validate 8-gate validator
/forge:commit commit
ASK /forge:health KB freshness + store integrity
/forge:status Sprint + task status
/forge:ask