--- title: "Facilitator Guide" description: "Minute-by-minute script for running the workshop." author: "Joey Lopez" date: "2026-01-18" tags: ["prompting", "teaching"] atom_id: 12 source_html: "bootcamp-facilitator.html" url: "https://jrlopez.dev/p/bootcamp-facilitator.html" generated: true --- [← home ]()[bootcamp ]()[S1 setup ]()[S1 flow ]()[S2 setup ]()[S2 flow ]()[success metrics ]() # Facilitator Guide Minute-by-minute timing, file usage, and coaching notes for professional workshop delivery Joey Lopez · Prompt Engineering Bootcamp · Internal use [session 1 setup ]()[session 1 flow ]()[session 2 setup ]()[session 2 flow ]()[success metrics ]()Session 1 ## Pre-Session 1 Setup (15 minutes before start) - Demo persona descriptions open and ready to share screen (3 personas visible) - Priority Builder Agent prompt (325 lines) copied to clipboard for AI tool demo - Session 1 slides opened and tested (diagrams displaying correctly) - AI tool open — ChatGPT or Claude with a fresh session - Quick reference cards available for participants (print or digital) Session 1 — Minute by Minute ## Session 1: Industry Standards (60 minutes) 0–5 min Problem & Solution Overview #### Materials None — pure presentation. Energy check. 0:00 — Welcome, energy check, agenda overview 0:02 — "How many use AI tools daily?" (show of hands) 0:03 — Show problem slide: "Let's see if this sounds familiar..." 0:04 — Build energy: "Today you'll learn systematic approaches" 0:05 — Transition: "First, let me show you three valid approaches" **Goal: **High energy, validate pain points. Don't solve the problem yet. 5–15 min Three Approaches Framework #### Materials Three Approaches diagram on screen. 5:00 — Show Three Approaches diagram 5:01 — Green path: "Most teams start here — ADRs + Config" 5:03 — Orange path: "Learning teams benefit from Structured" 5:05 — Yellow path: "Platform-committed teams use Tool-Assisted" 5:07 — Hands: "Who uses multiple AI tools?" → Point to green 5:09 — Hands: "Who wants to learn systematic prompting?" → Point to orange 5:11 — Hands: "Who's committed to one IDE like Cursor/Windsurf?" → Yellow 5:13 — Key insight: "All valid — choose based on team context" 5:15 — Transition: "Before we try this, let's see the foundational patterns" **Interaction: **Point, trace paths, ask team context questions. Don't rush. 15–20 min Foundational Patterns #### Materials Foundational Patterns diagram. Preview priority-builder prompt (mention it uses all 4 patterns). 15:00 — Show Foundational Patterns diagram 15:01 — Trace flow: "Persona establishes expertise..." 15:02 — "Few-shot shows desired format..." 15:03 — "Template structures the output..." 15:04 — "Chain-of-Thought reveals reasoning..." 15:05 — Quick interaction: "Where have you seen these before?" 16:00 — "In 5 minutes, you'll see all 4 patterns in a 325-line system" 17:30 — Transition slide to hands-on 20–25 min Demo: Priority Builder #### Critical File Sequence - Open demo personas on screen — show "Option B: Tech Lead" - Switch to AI tool with Priority Builder prompt pasted - Point out pattern locations: "Lines 1–4 are Persona, lines 200–220 Few-shot..." - Start 20 Questions — let AI ask 3–4 questions - Answer as Tech Lead persona: "AI/ML specialist, banking automation..." - Generate output — show CSV + formatted versions 20:00 — "I'll demo using a safe practice persona" 20:30 — OPEN persona descriptions on screen 21:00 — Point to Tech Lead: "5 years, AI/ML specialist, current projects..." 22:00 — "Now watch all 4 patterns in action" 22:15 — SWITCH to AI tool with prompt loaded 23:00 — Start 20 Questions, answer as Tech Lead 24:00 — Generate output: show CSV + formatted versions 24:30 — "Notice systematic vs ad-hoc difference" 25:00 — Transition: "Your turn — start with freestyle" - Participants see clear persona usage - AI generates realistic CSV output - All 4 patterns demonstrated and named - Systematic vs ad-hoc contrast is obvious 25–35 min Exercise: Freestyle First #### Materials Demo persona descriptions on screen for participant reference. 25:00 — "Choose a DIFFERENT persona from the demo" 25:30 — Show personas on screen again 26:00 — "Create 1 priority using your normal prompting approach" 26:30 — Circulate, observe struggles 27:00 — Coach lightly: "What metrics could you include?" 29:00 — Watch for pain points: vague results, generic language 30:00 — "2 more minutes" 32:00 — Quick debrief: "How many got output you'd submit to a manager?" 33:00 — "Most struggled with specificity — let's try systematic approach" 35:00 — Transition: "Now use Priority Builder methodology" #### Coaching note Don't help too much during freestyle. Let them feel the pain. Take mental notes of specific struggles for the debrief — the contrast will land harder. 35–50 min Exercise: Priority Builder Template #### Critical File Sequence - Participants copy/paste Priority Builder prompt into their AI tool - Switch to different persona than freestyle round - Guide through 20 Questions process 35:00 — "Everyone load the Priority Builder prompt" 35:30 — Verify: "Can you see the full 325-line prompt?" 36:00 — "Pick DIFFERENT persona from freestyle round" 36:30 — Walk around: ensure prompt loaded correctly (common paste issues) 37:00 — "Let the AI ask you questions — answer as your persona" 37:30 — Coach: "Be specific about projects and metrics" 40:00 — Watch for systematic vs ad-hoc differences emerging 42:00 — "Generate your priority — pick Conservative, Balanced, or Aspirational" 44:00 — "Anyone getting CSV output? That's ready for submission" 46:00 — Celebrate: "Show of hands who got specific metrics" 48:00 — Quick sharing: "What's one metric you wouldn't have thought of?" 50:00 — Transition: "Let's compare the three approaches" **Heavy coaching required here. **Ensure prompts load, guide specific persona-based answers, celebrate systematic outputs vs earlier freestyle struggles. 50–55 min Compare: Three Approaches 50:00 — "Same Spring migration, 3 different approaches" 50:30 — Show ADRs approach: simple prompt referencing standards doc 51:00 — Show Structured approach: multi-file systematic workflow 52:00 — Show Tool-Assisted: Windsurf 290-line cascade 53:00 — "Notice: same result, different maintenance overhead" 54:00 — Quick poll: "Which fits your team's style?" 55:00 — Transition to insights 55–60 min Insights & Session 2 Preview 55:00 — "What did you observe? Freestyle vs Priority Builder?" 55:30 — Capture insights: "Systematic = specific, ad-hoc = generic" 56:00 — "For Session 2: same patterns for interview prep" 56:30 — Preview job descriptions: "4 realistic senior roles available" 57:00 — "Bring: chosen job + same persona for continuity" 58:00 — Session 2 preview: "ReAct + Tree of Thoughts in action" 59:00 — "Questions before 5-minute break?" 60:00 — End Session 1 Session 2 ## Pre-Session 2 Setup - Job descriptions (4 options) open and visible - Demo persona descriptions — same personas from Session 1 - Interview prep 4-file workflow templates ready - Spring migration files loaded for live Java demo - Session 2 slides tested Session 2 — Minute by Minute ## Session 2: Advanced Patterns (60 minutes) 0–5 min Recap + Advanced Patterns Overview 0:00 — "Session 1 quick wins — who got CSV output?" 0:30 — "Today: same patterns for complex reasoning" 1:00 — Energy check: "Ready to level up?" 2:00 — "Advanced patterns: ReAct + Tree of Thoughts + live Java demo" 3:00 — "Goal: systematic methodology across ALL domains" 5:00 — Ready for advanced patterns 5–15 min Spec-Kit + ReAct + Tree of Thoughts 5:00 — Show Spec-Kit diagram 5:30 — Point to knowledge-base: "Reusable domain expertise" 6:00 — Point to specification: "This task's specific requirements" 7:00 — Point to implementation-plan: "Where ReAct + Tree of Thoughts live" 8:00 — "Key advantage: separation of concerns" 10:00 — Show ReAct + Tree diagram 10:30 — Trace ReAct flow: "Think → Act → Observe" 11:00 — Show Tree of Thoughts: "Generate → Evaluate → Choose" 12:30 — Interactive: "How would you analyze job requirements?" 15:00 — Transition: hands-on time 15–25 min Demo: Interview Prep Workflow #### Critical File Sequence - Open job descriptions — show "Senior Manager AI Strategy" role - Use same Tech Lead persona from Session 1 - Load interview prep 4-file workflow live 15:00 — "Interview prep using same Tech Lead persona from priorities" 15:30 — OPEN job descriptions, show Senior Manager AI Strategy role 16:00 — "Notice: 8+ years experience, $5M budget, C-level presentations" 16:30 — "Our Tech Lead: 5 years, AI specialist, no big budget experience" 17:00 — "Watch systematic gap analysis" 18:00 — Live spec creation: role details + background analysis 19:00 — Execute ReAct: "Think: Gap in budget management experience" 19:30 — "Act: Position as technical depth with business impact" 20:00 — "Observe: Need evidence of strategic thinking" 20:30 — Tree of Thoughts: 3 strategies: Technical Expert, Strategic Leader, Bridge 21:30 — Choose strategy: "Bridge Role — technical depth + business growth" 22:00 — Generate materials: positioning statement + STAR examples 23:00 — "Notice: systematic vs random interview prep" 25:00 — Transition to exercise - Clear job analysis demonstrated - ReAct pattern execution visible and named - Tree of Thoughts evaluation shown with explicit tradeoffs - Systematic positioning strategy emerges visibly 25–40 min Exercise: Build Interview Strategy #### File Coordination Participants pick a different job than the demo. Use the same persona from Session 1 priorities. 25:00 — "Everyone open job descriptions" 25:30 — "Pick DIFFERENT job than AI Strategy demo" 26:00 — "Options: Banking Consultant, Retail Director" 26:30 — "Use SAME persona from Session 1 for continuity" 27:00 — "Phase 1: Create specification.md" 27:30 — Coach: "Document job requirements vs your persona background" 28:00 — "What's the biggest gap?" 30:00 — "Phase 2: ReAct analysis" 30:30 — Guide: "THINK about positioning options" 31:00 — "ACT: Map specific experience to requirements" 31:30 — "OBSERVE: What positioning emerges?" 32:00 — "Tree of Thoughts: generate 3 positioning strategies" 33:00 — Coach: "What are pros/cons of each?" 34:00 — "Which has lowest risk?" 35:00 — "Generate positioning statement + 2 STAR examples" 38:00 — Celebrate: "Who has clear positioning strategy?" 40:00 — Transition: "Same patterns in technical work" #### Intensive coaching required - Guide explicit ReAct structure — many participants skip steps - Force specific evidence for positioning claims, not assertions - Help evaluate tradeoffs between strategies explicitly - Ensure STAR examples are specific, not generic 40–55 min Live Java Demo: Spring Migration #### Materials Screen share Spring migration repository. Cross-Domain Patterns diagram. 40:00 — "Same systematic patterns for technical work" 40:30 — Show Cross-Domain diagram: "Universal patterns across domains" 41:00 — SCREEN SHARE Spring migration files 41:30 — "Three approaches to same migration challenge" 42:00 — Show ADRs approach: .github/copilot-instructions.md 42:30 — "Simple prompt: 'Follow migration standards, update UserController'" 43:00 — Show Structured approach: spec/ folder workflow 44:30 — Execute live: Load files in AI tool, generate migrated code 46:00 — Point out ReAct: "Think dependencies → Act on imports → Observe compile" 47:00 — Show Tool-Assisted: Windsurf 290-line cascade 48:00 — "Built-in systematic validation at each step" 49:30 — "Same patterns: priorities → interviews → code" 51:00 — "ReAct works everywhere: Think → Act → Observe" 53:00 — Interactive: "Where else could you apply these patterns?" 55:00 — Transition to wrap-up - Clear pattern recognition across domains visible - Live code generation working in real time - "Aha moment" — universal patterns click for participants 55–60 min Integration + Next Steps 55:00 — "What patterns did you recognize across domains?" 55:30 — Capture: "Same ReAct, different applications" 56:00 — "This week: apply ReAct to one work decision" 56:30 — "Use Tree of Thoughts for next strategic choice" 57:30 — Show quick reference cards: "Take this for ongoing use" 58:00 — "Goal achieved: systematic vs ad-hoc methodology" 58:30 — "Questions? Discussion? Applications?" 60:00 — End workshop Evaluation ## Workshop Success Metrics #### Session 1 - 80%+ generate CSV-ready priorities - Clear systematic vs ad-hoc recognition - Proper persona usage throughout - Understanding of Three Approaches decision framework #### Session 2 - ReAct analysis executed properly (steps named) - Tree of Thoughts with explicit tradeoff rationale - Pattern recognition across business + technical domains - Confidence applying methodology to their own work #### Overall - Real deliverables created (priorities + interview materials) - Systematic methodology internalized - Cross-domain pattern recognition achieved - Concrete action plans for ongoing application Joey Lopez · 2026 · [jrlopez.dev ]() [← home ]()· [bootcamp overview ]()· [session 1 ]()· [session 2 ]()· [participant materials ]()· [quick reference ]()[.md ]()