Langerrr/zforge

README preview

# zforge

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

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 `compound-engineering:ce-debug`, and general code review to the host's code review plus `compound-engineering:ce-review`. zforge names those where they apply and owns none of them.

## Workflows

| Workflow | Claude Code | Codex | Description |
|----------|-------------|-------|-------------|
| Plan | `/zforge:plan <name> [--spec file] [--kind ...]` | `$zforge:plan` or “Use zforge to plan…” | Resolve a completeness contract, then write the artifact tree |
| Orchestrate | `/zforge:feature-orchestrate <name>` | `$zforge:feature-orchestrate` | Autonomous multi-phase execution with evidence-based acceptance |
| Resume | `/zforge:feature-resume <name>` | `$zforge:feature-resume` | Interactive implementation with check-ins between phases |
| Review | `/zforge:review --feature <name>` | `$zforge:review` | Check the implementation against the feature's own ledger |
| Debug | `/zforge:debug` | `$zforge:debug` | Route a concrete failure through the right debugging methodology |
| Track | `/zforge:track <name>` | `$zforge:track` | Progress, standing flags, and decisions awaiting review |
| Status | `/zforge:plan-status` | `$zforge:plan-status` | Feature status across the workspace |
| Retro | `/zforge:retro <name>` | `$zforge:retro` | Score zforge's own performance on a completed feature |

## How it works

View full repository on GitHub →