Installation
One command to install, then your first run end to end.
Quick start
npx slashforgeThat installs the guide files and the four commands into ~/.claude/. Open
Claude Code in any repo and type / — you should see /slashforge:setup,
/slashforge:code, /slashforge:investigate, and /slashforge:review-pr.
Your first run
Start to finish, for a repo that has never used SlashForge.
1. Install SlashForge.
npx slashforge2. Set up the repo. SlashForge ships every discipline skill the workflow uses, so there is no plugin step. See Skills for what runs at each phase.
3. Set up the repo. Open Claude Code in your project and run:
/slashforge:setupIt explores the codebase, asks you questions in batches, and generates
CLAUDE.md plus .claude/ rules, agents, skills, and hooks. This is also where
Graphify is offered, if your languages are supported — say no and it skips
silently.
4. Do some work.
/slashforge:codeIt asks what you want to build, then walks the ten phases, stopping at four
points for your approval. For a small change, add -quick.
5. Check it landed.
npx slashforge statusThat’s the whole loop. /slashforge:setup once per repo, /slashforge:code per
change, /slashforge:review-pr to review
someone else’s, and /slashforge:investigate
when you need to understand a bug before touching it.
Requirements
- Node.js 18+
- Claude Code
That is all SlashForge itself requires.
Optional integrations
Two, and neither has to be installed first. This trips people up, so to be explicit:
| Required? | When you deal with it | |
|---|---|---|
| superpowers | No — nothing invokes or checks for it | Never prompted for. Install it only if you want its own library |
| Graphify | No, fully optional | /slashforge:setup offers it mid-run, on supported languages only |
You do not need to prepare anything. Install SlashForge, run a command, and it will offer what it needs when it needs it.
Graphify is a Python CLI, so accepting that one needs Python 3.10+ and uv
(or pipx/pip) on your machine. Nothing to do up front — the
Graphify page covers the prerequisites and the
optional extras when you get there.
More
The package has a small CLI beyond the install command — status, uninstall,
project-mode vendoring, and the non-interactive flags for CI. All of it is on the
CLI reference.