Everyone leaves with the same picture of what vibe coding is, where it works well and where it goes wrong, and the team agrees one rule for what it builds.
Read Days 1, 3 and 7 (about five minutes each), or Module 1 on the cheat sheet.
One-word round: what's one small tool you wish you had at work?
Each person names one tool or fix they'd like built. Put each one in a column: sweet spot, needs guardrails, or get engineers (Day 3). Disagreements are the useful part: talk them through.
Each person picks one sweet-spot idea and writes the three-sentence brief from Day 7: who it's for, what it does, what done looks like.
Agree the team rule: “Prototype anything. Ship carefully. Know your red zone.”
Clicking yes to every permission prompt because it's faster (Day 6). Remind people the prompts are their seatbelt, and they should read them.
A whiteboard or shared doc with three columns, and a timer.
Next session: Module 2 · Setup. Bring the three-sentence brief from this week's action.