This is the frozen Claude 4 generation edition of Forge. It installs into Claude Code and gives you a single command, /forge4, that carries a project from a blank folder all the way to a tagged release. It works out what phase you are in, asks the right questions until it understands the problem, sets up the toolchain, then builds the thing test-first, keeping enough written state that you can walk away and pick up later in a fresh session.
On a Claude 5 model (Opus 5, Fable 5)? Use forge-workflow (/forge) instead, which is leaned out for v5. Both install side by side from the same dailen catalog, so keep whichever fits your model.
New here? Read the illustrated guide: https://daileng.github.io/forge4-workflow/
Install
claude plugin marketplace add DailenG/dailens-claude-toolbelt
claude plugin install forge4-workflow@dailen
Prefer a manual install? Download forge4-workflow.zip below and extract it to ~/.claude/skills/forge4-workflow/ (%USERPROFILE%\.claude\skills\forge4-workflow\ on Windows).
Added
/forge4orchestrator command: detects the current phase, reconciles the recorded state against the repository, and does the next thing.- Phase 1 (
/forge4-spec): requirements discovery to 95 percent confidence, producingdocs/SRS.mdbehind a mandatory approval gate. - Phase 2 (
/forge4-env): toolchain and repository bootstrap, testing harness, git hooks, and CI. Windows and PowerShell specific today. - Phase 3 (
/forge4-code): test-driven implementation in vertical slices, branch per slice, with a pre-push gate running build, tests, lint, and a secret scan. forge4-standards: always-loaded engineering standards covering typography, testing discipline, git lifecycle, and resumability.- SessionStart, PreToolUse, PostToolUse, and Stop hooks for state injection and drift detection, backed by four Node scripts.