This repository is a staged workshop, not a normal single-state app repo.
main is the shared workshop bootstrap. The current demo track is the desk
booking app, delivered through namespaced stage branches under
workshop/desk-booking/*.
- Verify Codex CLI
codex exec "Tell me a dad joke"- Clone this repo
git clone git@github.com:dickymoore/bmad-6-workshop.git
cd bmad-6-workshop- Install BMAD stable v6
npx bmad-method@latest install- Choose
Codexwhen prompted. - In Codex, run
/skillsfirst and confirm BMAD skills are listed. - Then invoke
bmad-help(for example$bmad-helporRun bmad-help) to get guided next steps across agents and workflows. - Do not rely on
/bmad-help; it may be unrecognized depending on Codex version/runtime.
- Start the desk-booking workshop track
git checkout workshop/desk-booking/10-analysis- Compatibility names still work while the refactor settles:
- old canonical:
workshop/10-analysis - legacy alias:
stage-1
- old canonical:
- Start the workshop
- Open
README.mdon the current branch. - Follow the stage instructions in order.
Desk-booking branch progression:
main -> workshop/desk-booking/10-analysis -> workshop/desk-booking/20-planning ->
workshop/desk-booking/30-solutioning -> workshop/desk-booking/40-implementation-setup ->
workshop/desk-booking/50-ready-for-dev -> workshop/desk-booking/60-implementation ->
workshop/desk-booking/70-complete -> workshop/desk-booking/80-mvp
Compatibility mappings still accepted by the helper scripts:
workshop/10-analysis->workshop/desk-booking/10-analysisworkshop/20-planning->workshop/desk-booking/20-planningworkshop/30-solutioning->workshop/desk-booking/30-solutioningworkshop/40-implementation-setup->workshop/desk-booking/40-implementation-setupworkshop/50-ready-for-dev->workshop/desk-booking/50-ready-for-devworkshop/60-implementation->workshop/desk-booking/60-implementationworkshop/70-complete->workshop/desk-booking/70-completeworkshop/80-mvp->workshop/desk-booking/80-mvpstage-1->workshop/desk-booking/10-analysisstage-2->workshop/desk-booking/20-planningstage-3->workshop/desk-booking/30-solutioningstage-4->workshop/desk-booking/40-implementation-setupready-for-dev->workshop/desk-booking/50-ready-for-devimplementation-in-progress->workshop/desk-booking/60-implementationcomplete->workshop/desk-booking/70-completemvp->workshop/desk-booking/80-mvp
The track definitions now live under workshops/. The current default track is
desk-booking, which is defined in workshops/desk-booking/track.json.
Additional scaffolded track:
albemarle-pulse- participant start:
workshop/albemarle-pulse/10-analysis - rolling authoring branch:
authoring/albemarle-pulse - track definition:
workshops/albemarle-pulse/track.json - facilitator showcase on
main:showcase/albemarle-pulse/ - showcase flow includes
00-pre-install/,installation/, and stage snapshots through80-mvp/
- participant start:
agent-replayis a separate sidecar repository, not a tracked file tree insidebmad-6-workshop.- Facilitator workspaces clone it alongside the exported workshop files as
agent-replay/. - Do not expect
agent_replay.pyto exist anywhere under this repo unless you have copied it in manually.
For facilitators and operators preparing or delivering the workshop:
workshop-setup-runbook.md: setup, troubleshooting, and reset workflow.workshop-branch-strategy.md: track model, branch flow, and compatibility policy.workshop-dry-run-and-delivery-checklists.md: dry-run and day-of delivery checklists.scripts/workshop-preflight.sh: readiness checks.scripts/setup-workshop-session.ps1: Windows session preparation and launch.scripts/setup-workshop-session.sh: bash session preparation and launch.scripts/export-workshop-showcase.sh: generate a no-branch-switch facilitator view onmain.workshop-video-script.md: facilitation script for demo recording or live delivery.
- Purpose: readiness check for the repo, environment, and track branches.
- When to run: before a dry-run, before facilitation, or after pulling major changes.
- Example:
./scripts/workshop-preflight.sh --track desk-booking --strict- Purpose: audit branches for legacy BMAD markers and missing stable-v6 structure.
- When to run: after migration changes or before merging workshop branch updates.
- Example:
./scripts/audit-bmad-v6.sh --track desk-booking --all --show-hits- Purpose: verify required and forbidden files for each stage in a track.
- When to run: after editing branch content, READMEs, or reviewer guidance.
- Example:
./scripts/verify-bmad-v6.sh --track desk-booking --all --show-failures- Purpose: facilitator review script with stage checks, guidance, and
--dev/--e2esmoke paths. - When to run: during prep, branch QA, and final rehearsal.
- Example:
./workshop-reviewer.sh --track desk-booking --all- Purpose: automate one workshop delivery session on Windows with
prepare/launch/desktops/all/teardownmodes. - When to run: before each rehearsal or live delivery slot.
- Example:
./scripts/setup-workshop-session.ps1 -Track desk-booking -Mode all -Session Wed-AM- Purpose: bash parity for one-session setup and teardown.
- When to run: from Linux/macOS/WSL when you want the same per-stage worktree layout.
- Example:
./scripts/setup-workshop-session.sh --track desk-booking --mode all --session Wed-AMSee scripts/README.md for more detail.
workshop/desk-booking/10-analysisthroughworkshop/desk-booking/50-ready-for-devdo not run the app from repo root. The floorplan demo lives inoffice-floorplans/(Next.js).workshop/desk-booking/60-implementation,workshop/desk-booking/70-complete, andworkshop/desk-booking/80-mvprun the desk-booking app from repo root (Vite).
The floorplan source files live in office-floorplans/.
- JSON data:
office-floorplans/assets/floorplans/offices.json - Render and demo code:
office-floorplans/src/andoffice-floorplans/scripts/ - Generated PNGs:
office-floorplans/demo-*.png
Run the demo locally:
cd office-floorplans
npm install
npm run dev
# open http://localhost:3000/demo-floorplans