s7-B1-1 pb-cover Polish your PRD
Write · critique · lock — tonight's spec is what your group builds against during the break.
Polish your PRD — write, critique, lock
s07 · Betterworks · 90m · Full Cohort ·
draft
s07 → 5 blocks, 15 slides, 10 trainer notes, 2 exercises, 1 reflects, 0 quizzes, 1 asides
Pre-read
- Find your group's **PRD shell from S06** — open the [S06 gdoc](https://docs.google.com/document/d/1Sos_1_zpDWrLtACOwPk8shd3AEVp9uvWgbt_O1Ky6yc/edit), locate your section, read it cold
- Have your **S05 design Critic Skill** invocable in claude.ai (designers)
- Have your **M1 skill** working in claude.ai or Claude Code (PMs)
- Open the **S06 gdoc** (same doc — link in your cohort home) — the `Skills` tab will have two skills ready to copy: a cohort-built PRD-writing skill + a PG-seeded PRD-critique skill
- Bring your **brand-voice.md** from the S05 bundle — the critique runs against it
No essays. Show up with your group's PRD shell open + your S05 Skill working.
- Have your **S05 design Critic Skill** invocable in claude.ai (designers)
- Have your **M1 skill** working in claude.ai or Claude Code (PMs)
- Open the **S06 gdoc** (same doc — link in your cohort home) — the `Skills` tab will have two skills ready to copy: a cohort-built PRD-writing skill + a PG-seeded PRD-critique skill
- Bring your **brand-voice.md** from the S05 bundle — the critique runs against it
No essays. Show up with your group's PRD shell open + your S05 Skill working.
Session goal
By end-of-session each group has:
1. **A developed PRD** — written from their S06 shell using a cohort-built PRD-writing skill, sitting in their gdoc section
2. **Two critique passes** — one for ship rigor (PRD-critique skill) + one for persona fit (their S05 Critic Skill applied to a new artifact)
3. **A locked, polished PRD** — revisions applied, ready for the build break to prototype against
4. **Cross-functional handoff complete** — PMs hammered for rigor, Designers hammered for persona; same artifact, both lenses
The arc: write → critique × 2 → refine → lock. Same compound pattern from S05, applied to PRDs.
1. **A developed PRD** — written from their S06 shell using a cohort-built PRD-writing skill, sitting in their gdoc section
2. **Two critique passes** — one for ship rigor (PRD-critique skill) + one for persona fit (their S05 Critic Skill applied to a new artifact)
3. **A locked, polished PRD** — revisions applied, ready for the build break to prototype against
4. **Cross-functional handoff complete** — PMs hammered for rigor, Designers hammered for persona; same artifact, both lenses
The arc: write → critique × 2 → refine → lock. Same compound pattern from S05, applied to PRDs.
Bridge from S06 · open the S07 gdoc
13 itemsOpen cold. S06's PRD shells in hand. Tonight we polish them. Reflection callback before we dig in.
s7-B1-2 list Where S06 landed · where tonight goes
We picked the idea together on Wednesday. Tonight we sharpen it for shipping.
- S06 ✓ — one group · one PRD shell · one idea to work through
- S07 tonight — write · critique × 2 · refine · lock
- Build break ahead — we build the M2 prototype against this PRD · self-paced M1/M2/M3 modules alongside
- Showcase destination — demo to senior leadership · credentials earned
s7-B1-3 gallery Big drops at Figma Config 2026
Where the design-to-code frontier is moving — the backdrop for tonight's mobile prototyping with AI.
s7-B1-4 activation Before we start — your S06 reflection
Open your S06 page · reflection + rating · anonymous OK.
s7-B1-5 activation Group check-in · 30 sec
Theme name · who's in the room · who's absent tonight.
s7-B1-6 activation Open the S06 gdoc · find your group's section
Skills tab has tonight's tools. Group A · B · C tabs are where the work lands.
Write — develop the PRD from your group's S06 idea
2 itemsThe cohort-built PRD-writing skill drives B2. One PM in the cohort brought a working PRD skill to S01 — tonight it becomes everyone's tool.
s7-B2-1 pb-section From shell to spec
Critique — two skills, parallel, same PRD
7 itemsThe headline beat. Two skills run on one artifact. PMs hit ship rigor; Designers hit persona fit. Same compound pattern as S05 — build a skill once, reuse it on new inputs.
s7-B3-1 list The PRD-critique skill · four dimensions
The PRD-critique skill hits PRDs the way the Critic Skill hits screens.
- Edge cases — at scale · error states · weird inputs · unexpected behaviour
- Boundary conditions — limits · timeouts · max items · rate limits · data constraints
- UX — flow integrity · accessibility · empty/loading/error coverage
- Copy — apply brand-voice.md · flag off-brand · rewrite worst 2–3 phrases
s7-B3-2 code The PRD-critique skill
s7-B3-3 gallery Meanwhile · at Config this week
Code is coming to the canvas. Design-to-code gap closing in the tool itself.
Refine + lock — apply findings, ship the spec
2 itemsEach group revises the v1 PRD against the consolidated critique. Lock by end of block.
s7-B4-1 pb-section Apply the findings · lock the spec
Walk · credential frame · S08–S10 preview · close
13 itemsEach group walks their locked PRD. Certificate moment lands. Build break framed. pb-thankyou.
{/* ───── B5 · Variant A · Option 1 (self-paced + 06-Jul review + offsite showcase) ───── */}
s7-B5-1 list Showcase · what it looks like
60 min · demo to leadership · credential ceremony · the practice's promise lands.
- Opening (5 min) — PG opens · the practice's promise · the build-break frame
- Demos (40 min) — group demo · 7 min M1 → M2 → M3 walk + 5 min leadership Q&A
- Cohort reflection (5 min) — voices from the room · what changed · what's next
- Credential ceremony (5 min) — AI-Native Practitioner — Product & Design (Level I) · delivered live
- … 1 more
{/* ───── /B5 · Variant A ───── */}
{/* ───── B5 · Variant B · Option 2 (break + remaining live + 20–23 Jul showcase) ───── */}
{/* ───── B5 · Variant B · Option 2 (break + remaining live + 20–23 Jul showcase) ───── */}
s7-B5-2 list What's ahead · build break + self-paced + showcase week
Build the prototype during the break · master M1/M2/M3 self-paced · clinic + showcase to close.
- Build break (26 Jun → 12 Jul) — build the M2 prototype against the locked PRD · 4 hr coaching budget
- Self-paced Mastery unlocks during the break — M1 (Mon 29 Jun) · M2 (Wed 1 Jul) · M3 (Mon 6 Jul) · each ends with a quiz + artifact gate
- S08 (Mon 13 Jul) · Capstone clinic — 60 min — sharpen what the rubrics couldn't judge · taste · framing · demo flow
- Showcase (20–23 Jul window · 60 min) + 30-min cohort-only pre-arrival · demo to leadership · credentials
s7-B5-3 list Showcase day · 20–23 Jul window
30-min cohort pre-arrival · then leadership arrives · 60-min programme.
- Pre-arrival (30 min) — Cohort arrives · laptops set up · lightning dress rehearsal of opens + closes
- Opening (5 min) — Leadership arrives · PG opens · the practice's promise · the build-break frame
- Demos (45 min) — group demo(s) · 7 min M1 → M2 → M3 walk + 5 min leadership Q&A · per group
- Cohort reflection (5 min) — voices from the room · 30 sec each · what changed, what's next
- … 1 more
{/* ───── /B5 · Variant B ───── */}
s7-B5-4 pb-thankyou (no title)
After this session
- **Your group's PRD is locked in the S07 gdoc** — your group builds the M2 prototype against this during the break
- **Wiring tier is named** — if T2 (sheet), one group member sets up the sheet by end of week. If T1 (BW API), confirm access is real before the break
- **Schedule coaching slots** with PG during the build break (4 hr budget per group) — drop preferred times in cohort chat by Friday
- **PRD-critique skill** — save the prompt to your account if you want to reuse it on other PRDs at BW (the skill came from the cohort; it's yours to keep)
- **Self-paced track** unlocks Mon 29 Jun (M1) · Wed 1 Jul (M2) · Mon 6 Jul (M3) — each ends with a quiz + artifact gate; both feed the S08 clinic
- **For S08 (Mon 13 Jul) · Capstone clinic:** show up with all three module artifacts saved to gdoc · rubric outcomes in hand · the question the rubrics couldn't answer
- **For S10 (Fri 17 Jul) · Showcase:** arrive 13:30 IST for cohort-only pre-arrival lightning dry-run; leadership at 14:00 sharp
- **Failure-mode recovery (trainer-side):**
- **B2 write pass produces sprawling v1 PRDs** — pre-empt: post in chat at min 25, *"v1 is complete enough to critique, not polished. Move on at min 30."*
- **B3 critique skills produce thin output** — name the contrast: *"PMs found ship gaps. Designers found fit gaps. Where are they DIFFERENT?"* The differentiation is the value.
- **B4 groups can't lock in time** — bias toward "lock with known open items" over "keep refining". Open items go in cohort chat for build-break work.
- **If Veronica isn't in the room** — PG seeds a PRD-writing skill from the pm-skills library in the S07 gdoc Sunday. Brief is the same.
---
## Open items (for polish pass / PG review)
1. **S07 gdoc URL** — `[?CONFIRM]` placeholder in B1 activation slide. PG creates Sunday with 4 tabs: `Skills · Group A ↓ · Group B ↓ · Group C ↓`. Skills tab pre-seeded with PRD-writing skill (Veronica's) + PRD-critique skill (PG-seeded).
2. **Pre-flight Veronica** — PG asks Sunday to confirm she's in the room + to share her PRD skill content for the Skills tab. Fallback: PG seeds a skill from the lean PM kit (`prompts/s06/lean-pm-kit/`).
3. **PRD-critique skill seed file** — write to `prompts/s07/prd-critique-skill.md` for git-tracked source. Same content as the B3 code slide. Stage script can ship it in a bundle if PG wants designers to save it to their accounts (optional — defer to PG's call).
4. **Figma Make access pre-flight for the build break** — PG asks in cohort chat the weekend after S07: *"who has Figma Make access?"* Fallback path documented in M3 Mastery module.
5. **Coaching slot calendar** — PG drops a Calendly link or coordinates over chat for 4 hr per group during the build break. Reference in B5 close.
6. **Activation count** — 5 activations across B1–B5 (S06 reflection · open gdoc · write pass · parallel critique · lock pass · walk) · 3 surfaces (link · gdoc · screen-share). Passes §17 floor for 90 min.
7. **Brand naming** — Lab/programme used throughout per §32. No "bootcamp" mentions. Cover slide eyebrow uses "Session 07 · M3 frame".
8. **§31 compliance** — no cohort-facing timing on slide headlines, subheads, or footnotes. Trainer notes carry pacing; `:::exercise{}` blocks omit duration (timing implicit from block range).
- **Wiring tier is named** — if T2 (sheet), one group member sets up the sheet by end of week. If T1 (BW API), confirm access is real before the break
- **Schedule coaching slots** with PG during the build break (4 hr budget per group) — drop preferred times in cohort chat by Friday
- **PRD-critique skill** — save the prompt to your account if you want to reuse it on other PRDs at BW (the skill came from the cohort; it's yours to keep)
- **Self-paced track** unlocks Mon 29 Jun (M1) · Wed 1 Jul (M2) · Mon 6 Jul (M3) — each ends with a quiz + artifact gate; both feed the S08 clinic
- **For S08 (Mon 13 Jul) · Capstone clinic:** show up with all three module artifacts saved to gdoc · rubric outcomes in hand · the question the rubrics couldn't answer
- **For S10 (Fri 17 Jul) · Showcase:** arrive 13:30 IST for cohort-only pre-arrival lightning dry-run; leadership at 14:00 sharp
- **Failure-mode recovery (trainer-side):**
- **B2 write pass produces sprawling v1 PRDs** — pre-empt: post in chat at min 25, *"v1 is complete enough to critique, not polished. Move on at min 30."*
- **B3 critique skills produce thin output** — name the contrast: *"PMs found ship gaps. Designers found fit gaps. Where are they DIFFERENT?"* The differentiation is the value.
- **B4 groups can't lock in time** — bias toward "lock with known open items" over "keep refining". Open items go in cohort chat for build-break work.
- **If Veronica isn't in the room** — PG seeds a PRD-writing skill from the pm-skills library in the S07 gdoc Sunday. Brief is the same.
---
## Open items (for polish pass / PG review)
1. **S07 gdoc URL** — `[?CONFIRM]` placeholder in B1 activation slide. PG creates Sunday with 4 tabs: `Skills · Group A ↓ · Group B ↓ · Group C ↓`. Skills tab pre-seeded with PRD-writing skill (Veronica's) + PRD-critique skill (PG-seeded).
2. **Pre-flight Veronica** — PG asks Sunday to confirm she's in the room + to share her PRD skill content for the Skills tab. Fallback: PG seeds a skill from the lean PM kit (`prompts/s06/lean-pm-kit/`).
3. **PRD-critique skill seed file** — write to `prompts/s07/prd-critique-skill.md` for git-tracked source. Same content as the B3 code slide. Stage script can ship it in a bundle if PG wants designers to save it to their accounts (optional — defer to PG's call).
4. **Figma Make access pre-flight for the build break** — PG asks in cohort chat the weekend after S07: *"who has Figma Make access?"* Fallback path documented in M3 Mastery module.
5. **Coaching slot calendar** — PG drops a Calendly link or coordinates over chat for 4 hr per group during the build break. Reference in B5 close.
6. **Activation count** — 5 activations across B1–B5 (S06 reflection · open gdoc · write pass · parallel critique · lock pass · walk) · 3 surfaces (link · gdoc · screen-share). Passes §17 floor for 90 min.
7. **Brand naming** — Lab/programme used throughout per §32. No "bootcamp" mentions. Cover slide eyebrow uses "Session 07 · M3 frame".
8. **§31 compliance** — no cohort-facing timing on slide headlines, subheads, or footnotes. Trainer notes carry pacing; `:::exercise{}` blocks omit duration (timing implicit from block range).
Add ?token=… to the URL.