Designing a delivery workflow
Built-in templates
-
New workflow (from scratch, 2 steps): Implement (auto-routed) → Done. Note that it has no review step, so PRs from it aren't reviewed unless you add one.
-
Default delivery workflow (6 steps): Plan / decompose (Engineering Lead) → Implement (auto-routed) → Code review (Code Reviewer; failure → Implement) → Human merge (human gate; failure → Implement) → QA (QA Engineer; failure → Implement) → Done. New workspaces start with this as the default.
-
Full delivery workflow (20 steps): Spec & acceptance criteria → Scope sign-off (human) → Architecture / ADR (skip → Plan) → ADR approval (human; failure → Architecture) → Plan / route / decompose → Implement (auto) → CI / quality gate (failure → Implement) → Code review (failure → Implement) → Security review (failure → Implement; skip → merge) → Human merge → QA (failure → Implement) → Documentation → Release prep → Deploy (staging) → Verify (staging; failure → Implement) → Production deploy approval (human) → Deploy (production) → Verify (production; failure → Implement) → Delivery report → Done. The shared finish starts at Documentation. It uses many roles (product analyst, architect, lead, devops, reviewer, security, QA, technical writer, SRE, delivery manager). Steps whose role isn't hired wait for a person, so hire those roles or remove the steps.
-
Agile AI-driven delivery: compatible with the BMad Method v6 (an open-source agile AI method; we're not affiliated). Three tracks:
- Quick (7 steps): Tech spec (Product Analyst, written to
docs/tech-spec.md) → Plan stories → Build (auto) → Code review → Human merge → QA → Done. - Method (12 steps): PRD (
docs/prd.md) → UX design (UX Designer,docs/ux-design.md; skips when there's no UI) → Architecture (docs/architecture.md) → Readiness check (Architect: do the documents agree? can pass with concerns) → Planning sign-off (human: merge the planning PRs; failure → PRD) → Plan stories → Build → Code review → Human merge → QA → Retrospective (Delivery Manager, once for the whole delivery) → Done. The shared finish starts at Retrospective. - Enterprise (22 steps): the Method track plus CI / quality gate, Security review, Documentation, Release prep, staged deploys with Verify, Production deploy approval, Delivery report and the Retrospective. The shared finish starts at Documentation.
- Quick (7 steps): Tech spec (Product Analyst, written to