V1 long-form archive. Pre-precision-pass version, preserved for engineers who prefer the dense narrative. New (V2) version: ../.
What It Gives You
- Shared private git repo per bundle of one or more Jira epics.
- Five role hats in one place: PO, Architect, Staff Eng, UX, QA.
- Three-stage lifecycle for every artifact:
draft → published → approved. - Single source of truth for ralph:
.workbench-state/approved.json. - Cross-repo ralph orchestration — plan and dispatch across multiple service + automation repos.
- One-way template updates — pull skill improvements from the
ai-workbenchtemplate without touching your outputs.
Two Repos, One Story
| Repo | Role |
|---|---|
ai-workbench |
Template. gh repo create --template stamps an instance per bundle. |
ai-devkit |
Global CLI. Provides init.wb, join.wb, update.wb. |
Quick Paths
- New to this? Start at Getting started.
- Want the architecture? Architecture.
- Want to understand state transitions? Artifact lifecycle.
- Looking for a specific skill? Skills reference.
- Ralph integration questions? Ralph integration.
- How steering works (golden principles, role rules, overlays)? Steering workflow.
- Update notifications + how to upgrade? Versioning + upgrades.
- Something unclear? 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 (generates per-repo fix_plans)
→ /ralph-dispatch (parallel autonomous execution)
License
See repo license files.