Team Formation + Project Kickoff
3 teams of 3 · working agreements · pitch
Block breakdown
What each session covers. Tier pills show when AI is off (A), foundation (B), or AI-default (C).
- B C
A — Recap + Homework Check
15 minChapter 2 work acknowledged, ideas visible, students oriented for the team announcement.
- A
B — Team Announcement
15 min3 teams of 3 formed, rationale understood, initial emotional reaction processed.
- B
C — Roles Explained
20 minStudents understand the three roles, the rotation rule, and how each role relates to Claude.
- B C
D — Team Ice-breaker
25 minTeam members know each other's working styles, strengths, struggles, and have 2-3 team norms established.
- C
E — Idea Evaluation Workshop
35 minEach team has narrowed to 2-3 candidate ideas evaluated against a concrete framework.
- A C
F — Wrap + Pitch Prep
10 minTeams have the pitch structure, understand the homework, and know what Session 2 brings.
- B C
A — Working Agreement Finalize
20 minEach team has a personalized working agreement committed to their repo.
- B
B — SDD Intro
5 minStudents understand the spectrum from vibe coding to spec-driven development and know why specs matter more in the AI era.
- B C
C — Team Pitches
35 minAll 3 teams have pitched, received feedback, and adjusted their project scope.
- C
D — Architecture Decision
30 minEach team has a documented stack decision (frontend, backend, database, deployment) with rationale.
- B C
E — Repo Setup + First Team Commit
20 minEach team has a GitHub repo with README, CLAUDE.md, .gitignore, and working agreement — all 3 members can push and pull.
- A
F — Week 1 Role Assignment
10 minEach team has Anchor/Builder/Driver assigned for Chapter 4, with a clear understanding of what each role does next week.