Prefer the old long-form? See V1 archive.

A per-bundle workbench: one private repo where a dev + QA pair carry one or more Jira epics from PRD to shipped code via ralph.

What you get

• Private git repo per bundle, shared between two collaborators.
• Five role hats in one place: PO, Architect, Staff Eng, UX, QA.
• Three-stage lifecycle for every artifact: draft → published → approved.
• Single ralph gate: .workbench-state/approved.json.
• Cross-repo orchestration: workspace-mode plan + parallel dispatch.
• One-way template updates: pull skill improvements without touching your outputs.

Two repos

Repo	Role
ai-workbench	Template. init.wb stamps a private instance per bundle.
ai-devkit	Global CLI: init.wb, join.wb, wb.upgrade.

Where to go

• New here → Getting started
• Lost in the pipeline → Workflows or wb.wtd (ref)
• Architecture / tree / manifests → Architecture
• State transitions → Artifact lifecycle
• Skills (20) → Skills reference
• Ralph integration → Ralph
• Steering (golden / role / overlays) → Steering workflow
• Upgrades + notifications → Versioning
• Stuck → FAQ

Typical flow

Jira epic → /epic-intake → publish + approve
         → /prd-draft   → publish + approve
         → /eng-spec    → publish + approve   (dev hat)
         → /tdd         → publish + approve
         → /bdd-gen     → publish + approve   (QA hat)
         → /test-cases-gen → publish + approve
         → /test-spec   → publish + approve
         → /ralph-workspace-plan
         → /ralph-dispatch

License

See repo license files.