Capstone · Days 12–15 · Cross-functional
Day 15 — Review, merge, demo — Final checkpoint
EveryoneCheckpoint
Morning — review and merge:
- Cross-review: dev reviews QA's test code; QA reviews a dev PR; BA checks merged behavior against the acceptance criteria — gaps become same-day tickets.
- Merge, tag a release, run the deploy; Remote-Control/Dispatch demo: approve and steer a session from a phone.
Afternoon — demo, retro, playbook:
- Each pair demos 10 minutes — the flow, not slides: ticket → plan → PR → review → tests → artifact → shipped.
- Retro: what to standardize (
CLAUDE.mdrules, skills, hooks, review checklist) — capture as repo issues owned by named people.
Exercise
Personal playbook: each person writes their one-page "how I work with Claude" — favorite workflows, prompts, guardrails — shared as artifacts.
Final checkpointCompany-ready
- Capstone shipped end-to-end.
- Every person has demonstrated their track's skill bar (Days 3/6/11 checklists all green).
Skills today
- Remote Control (/rc): Steer a session from your phone
How to set up
See Day 6 for the setup steps.
- Dispatch (phone-kicked Code sessions, push alerts; Pro/Max only): Hand a task over while commuting
How to set up
See Day 6 for the setup steps.
- Personal “how I work with Claude” playbook: Guardrails and favorite workflows, shared
How to set up
Nothing to install — a one-page document. Write your guardrails and favorite workflows and share it with the team (an artifact or the repo wiki works fine).
Related: Course catalog · Developer track · BA/QA track · Shared fundamentals