build-first-win-triggerlisted

# /build-first-win-trigger — Define First-Win Triggers per Cohort > **Purpose.** Define the first-win trigger for a cohort — the measurable, time-bound outcome each student archetype achieves in week 2-4 that proves the program works. Without first-win triggers, students lose conviction by week 4 and cohort retention crashes. Per Phase 3 plan, first-win rate target is ≥70% by week 8. > > **Bar.** First-win is the moment the student stops questioning the program and starts evangelizing it. Designed correctly, it's also the proof event that becomes the case study material for cohort-2 sales. ## When to invoke - During program-tier design (called by `/design-program-offer`) - Before each cohort launch (recalibrate first-win definitions to current curriculum + case study density) - After each cohort (review first-win rate; refine triggers if rate <70%) - When a new student archetype emerges (e.g., "consultant pivoting to agency" wasn't an archetype in cohort 1, becomes one in cohort 3 → new trigger needed) ## Required inputs 1. Curriculum spec from `/build-curriculum` (the modules first-wins derive from) 2. Pre-program intake data for the cohort (segment students into archetypes) 3. Prior cohort first-win achievement data (if applicable — informs trigger refinement) 4. Mentor capacity for verification (each first-win requires mentor sign-off) ## The build sequence ### Step 1 — Cohort segmentation by archetype Per cohort, identify 3-5 student archetypes. Common archetypes