Langerrr/zforge

README preview

# zforge

The durable state, contract and evidence layer for multi-session feature work in Claude Code.

zforge carries what must be true before a phase closes, what evidence proves it, what was decided along the way, and what is still open. It does not carry methodology — discovery belongs to `superpowers:brainstorming`, test discipline to `superpowers:test-driven-development`, debugging rigour to `superpowers:systematic-debugging` and `ce:debug`, general code review to `/code-review` and `ce:review`. zforge names those where they apply and owns none of them.

## Commands

| Command | Description |
|---------|-------------|
| `/zforge:plan <name> [--spec file]` | Resolve a completeness contract, then write the artifact tree |
| `/zforge:feature-orchestrate <name>` | Autonomous multi-phase execution with evidence-based acceptance |
| `/zforge:feature-resume <name>` | Interactive implementation with check-ins between phases |
| `/zforge:review --feature <name>` | Check the implementation against the feature's own ledger |
| `/zforge:debug` | Route a concrete failure through the right debugging methodology |
| `/zforge:track <name>` | Progress, standing flags, and decisions awaiting review |
| `/zforge:plan-status` | Feature status across the workspace |
| `/zforge:retro <name>` | Score zforge's own performance on a completed feature |

## How it works

View full repository on GitHub →