None. The work happened across the sessions and the build break. Tonight is the look back — and the look forward.
**Leadership (optional):** a two-paragraph one-pager from PG — what the cohort committed to, each group's PRD, and what M1 / M2 / M3 mean. Sent via the sponsor 24 hr ahead. [?CONFIRM PG drafts this.]
Session goal
By end-of-session:
1. **The room has seen the arc** — nine sessions as one spine, prompt to a wired prototype, credited to the cohort 2. **The cohort is credited for what they built** — real skills, a locked PRD, a working prototype, a prototype wired to real data 3. **Everyone knows the portal stays open for a year** — dockets, prompts, and their credential all live on 4. **The end-of-course check-in is logged** — baseline re-asked (each person's delta), a capstone debrief, and where they want to go next 5. **Twelve practitioners credentialed** — named, linked, and pointed at the next rung
B100–15
The arc · key takeaways across nine sessions
15 items
Open warm. A fast walk down the spine — for the cohort, it's how far they came; for leadership, it's the story behind the work. Nine sessions, three modules, one capstone.
▤ Slide · s10-B1-1pb-coverB1L21
The whole arc → what's next
Fourteen hours. Prompt to a shipped, wired prototype. A fast look back, then the look forward.
▤ Slide · s10-B1-2statementB1L32
Fourteen hours ago
A prompt was something you typed . Now it's context architecture — and there are skills, PRDs and working prototypes to prove it.
▤ Slide · s10-B1-3pb-sectionB1L45
Key takeaways
▤ Slide · s10-B1-4listB1L55
M1 · Backlog Intelligence
Sessions 1–3 — from someone's prompt to your own running skill.
S01 — prompts aren't typing, they're context architecture; structure is the lever, not the model
S02 — ran the AI cleanup chain on a real backlog, then agreed as a cohort on the one skill to maintain
S03 — built your own M1 skill; one command runs the chain on your machine
▤ Slide · s10-B1-5listB1L64
M2 · Design AI
Sessions 4–5 — the Design System as a guardrail, not an afterthought.
S04 — Claude refuses off-system tokens; the Critic pattern closes the 40% gap Figma's AI leaves on the floor
S05 — extracted your team's DS into Claude and packaged a persona-critique Critic skill into your own Claude.ai
S06 — picked your group's real Betterworks capstone PRD
S07 — the cohort's own skills hammered the PRD for ship rigor and persona fit; spec locked
S08 — a prototype is a question, not an artifact — fidelity is a dial, and AI made the top of it nearly free
S09 — the stack: Prompt → Skill → Tool → Connector → Agent; screens that read real data, no copy-paste
▤ Slide · s10-B1-7listB1L86
Your capstone — what you shipped
Not slides. Working artifacts — each of you has these, on your own machine.
An M1 backlog-intelligence skill — running on your own machine (S03)
Your team's Design System in Claude + a persona-critique Critic skill in your own Claude.ai (S05)
A locked, ship-rigor PRD — hammered by the skills you built (S07)
A working mobile prototype — fidelity dialled to the question (S08)
… 1 more
▤ Slide · s10-B1-8pb-sectionB1L101
Capstone presentations
B215–30
Questions · open floor
3 items
A held beat. The room has just seen the whole arc — leave real space for what it surfaced, from the cohort and from leadership.
▤ Slide · s10-B2-1pb-sectionB2L113
Questions?
B330–38
Stay connected · your portal for a year
5 items
Two beats: how to reach PG after the room closes, and the reminder that everything they built lives on.
▤ Slide · s10-B3-1customB3L127
(no title)
▤ Slide · s10-B3-2activationB3L146
Your portal stays open for a year
Every docket, every prompt, and your credential live at builder.prasadgupte.com/c/betterworks-jun26/ — bookmark it.
B438–45
Baseline → now · the 3-minute check-in
4 items
A cohort task in the room. Frame it as *their* delta first, then ask them to log it now, not later. (Leadership can use the moment as a natural breather before credentials.)
▤ Slide · s10-B4-1activationB4L161
3 minutes — the end-of-course check-in
Same baseline (your delta) · a capstone debrief · and where you want to go next. Link in the chat now.
B545–60
Credential · what's next · close
11 items
Close the loop with leadership in the room: name what each practitioner earned, point at the next rung, end warm.
▤ Slide · s10-B5-1statementB5L182
The AI-Native Practitioner credential
Awarded to every member who shipped: a PRD · a working prototype · a prototype wired to real data. Each named. Each linked. Each yours to cl
▤ Slide · s10-B5-2activationB5L196
Naming · credentialing
PG names each practitioner · credential link delivered live · in cohort-roster order.
▤ Slide · s10-B5-3ctaB5L211
You just finished Level I
Most AI training ends when the course does. This is a path — Level II · Architect builds the harness that runs your workflow without you in
▤ Slide · s10-B5-4listB5L222
Where to keep elevating
Your Level I workflow is the seed. Horizons to push into next — solo, then with your team.
Wire it to reality — connect your workflows to real systems via MCP (Jira · Aha! · Figma · your DS)
Make it trustworthy — evals that catch regressions before they reach review
Make it run without you — a harness a teammate can run cold (the empty-chair test)
Systematize your team — instrument shared workflows, not just your own
… 1 more
▤ Slide · s10-B5-5pb-thankyouB5L237
(no title)
After this session
- **Check-in responses in** — the end-of-course survey captures each person's full delta (vs. baseline + mid), the workflow-depth + harness-adoption layer, a capstone debrief, NPS, and the next-level + topics signal for the ladder - **Credentials released + delivered** — PG presses release during the ceremony; every practitioner has the credential link and PDF in their portal - **One-pager retrospective** — PG drafts a 1-page summary for the BW sponsor within 48 hr: what got built, the delta signal, where the practice could compound at BW - **What's-next follow-up** — PG reviews next-level.final + topics.interest to shape the sponsor conversation (Architect cohort for the team / on-demand for teammates / individual Level II) - **Cohort chat + portal stay open** — chat 30 days post-wrap; the bootcamp portal stays live for a year (extends with any further course) - **LinkedIn nudge** — PG asks each practitioner Sunday: *"if it landed, post your credential — tag the cohort and the programme"*
## Open items (for polish pass / PG review)
1. **Reshape (2026-07-22)** — S10 is now a clean recap → portal → check-in → credential **wrap**; the in-deck capstone showcase (group cards + three live-demo slides + baseline-recall slide) was removed per PG. If the live demos still happen this session, they sit outside this deck (own run-of-show). 2. **Duration** — left at 60 with a generous open-floor Questions block (15 min) and an unhurried credential ceremony. Trim the open floor if the slot is tighter. 3. **`check_in_final_open_at`** — set to the S10 date so the in-room check-in is open on the night (in `cohorts/betterworks-jun26.yaml`). 4. **Contact slide QR** — LinkedIn QR at `/images/s10/linkedin-qrcode.jpeg`; confirm it scans on the projected canvas at rehearsal. 5. **Credential ceremony** — roster order + press **release** (the new KV gate) before the naming so pages + PDFs reveal at once. Pre-flight the release button. 6. **Leadership** — attendee names/size for the open-floor Q&A + the one-pager. Optional one-pager sent 24 hr ahead. 7. **Survey (updated 2026-07-22)** — `check-in-final` bumped to v0.5.0: adds the workflow-depth block (workflow.confidence, harness.cowork/browser/claude-code, inspiration.expanded/next-build). Confirm the option wording. 8. **Status** — left at `draft`; not cohort-visible until you release S10.
Add ?token=… to the URL.
This site uses cookies to measure how content performs and to improve your experience.
No cookies are set until you choose.
Privacy policy
Cookie preferences
Choose which cookies you allow. Your choices are saved for one year.
You can change them anytime via the "Cookie settings" link in the footer.
Necessary
Always on
Required for the site to function. Includes your consent choice and security features like Cloudflare Turnstile. Cannot be disabled.
Analytics
Helps us understand how visitors use the site — which pages are popular, how you arrived, and where you drop off. Data is aggregated and anonymous.
Used by services like Google Analytics and Microsoft Clarity.
Marketing
Used to measure ad campaign effectiveness and show relevant content across platforms.
Used by services like Google Ads and Microsoft Advertising (UET).