Week 2 Facilitator Hand-Outs

Nine chat-paste-ready blocks for the Course 2 Builder Orientation session. Open this tab in a second window before the session, then copy each block into Microsoft Teams chat at the slide it pairs with.

← Back to Week 2 Slide Deck Course 2 Instructor Page

How to use this page. Keep it open in a second browser tab. When the deck reaches the slide called out on each block’s gold pill, click Copy, then paste into the Teams chat. Plain text is intentional — it survives the Teams paste cleanly and stays legible on a 13″ laptop.

Print fallback. If you lose your second-screen, this page prints to one or two clean pages with the copy buttons hidden — use Ctrl+P / ⌘+P.

Where these come from. Each block is lifted verbatim from the Builder Orientation instructor page — the six narrated demo prompts in Module 2 (equipment-checkout build), the debugging template students use in Module 3, and the peer-review and decomposition worksheets for Modules 3 and 4.

Prompt 1: define the problem

First prompt of the live build. Drop it into chat as you narrate “I start with WHO uses this and WHAT platform we have. I ask for a plan, not code.” Students paste this into GenAI.mil at the same moment so they get the same plan back.

Use on Module 2 Prompt 1 slide Prompt 1: define the problem (2 min)
Cue line for the room: “Prompt 1 in chat. Paste it into GenAI.mil now. We are asking for a plan, not code.” 
I need an equipment checkout tracker for a Marine Corps rifle section (~30 people, ~50 items) in Microsoft Power Apps. It needs to: check out items (item name, serial, person, date out, date due), check in items, show all checked-out items, and highlight overdue ones. Give me a step-by-step plan before we build.

Prompt 2: create the data structure

Second prompt. The plan is on screen; now ask for the exact SharePoint list configuration plus a CSV template that imports cleanly.

Use on Module 2 Prompt 2 slide Prompt 2: create the data structure (3 min)
Cue line for the room: “Prompt 2 in chat. Now we get the data structure - field names and types. We specify because we know the domain.” 
Give me the exact SharePoint list configuration: list name, all columns with data types, and any calculated columns for overdue status. Include a CSV template I can import into SharePoint and tell me which columns I need to add manually after import.

Prompt 3: refine the interface

Third prompt. After Integrate → Power Apps generates the starter app, this prompt asks AI to filter the gallery, color overdue rows, and add a check-in button.

Use on Module 2 Prompt 3 slide Prompt 3: refine the interface (5 min)
Cue line for the room: “Prompt 3 in chat. Power Apps gave us a working app. Now we use AI to customize it - in plain English.” 
I used Integrate -> Power Apps -> Create an app from my EquipmentCheckout SharePoint list. The auto-generated app has BrowseGallery1 showing all items. I want to: filter the gallery to only show checked-out items, color overdue items in red, and add a check-in button next to each gallery row. Give me the formulas.

Prompt 4: iterate

Fourth prompt. Adds a search box and warning icon to the gallery. The teaching point is incremental refinement — we do not rebuild from scratch.

Use on Module 2 Prompt 4 slide Prompt 4: iterate (3 min)
Cue line for the room: “Prompt 4 in chat. Add the SearchBox and the icnOverdue icon in Power Apps first, then paste this.” 
I added a Text Input control named SearchBox above BrowseGallery1. I also added a Warning icon named icnOverdue inside each gallery row. Now update the gallery to: search by item name or assigned person, sort overdue items to the top, and show the warning icon only for overdue items.

Prompt 5: debug an error

Fifth prompt. The instructor introduces a deliberate error (Choice column without .Value, or a type mismatch) and demonstrates the debugging loop with the exact error message.

Use on Module 2 Prompt 5 slide Prompt 5: debug an error (4 min)
Cue line for the room: “Prompt 5 in chat. Errors are normal. Watch how AI diagnoses with exact error + exact code + intent.” 
I am getting this error: "Invalid argument type. Expecting a Text value instead." Here is my formula:

  Filter(EquipmentCheckout, Status = "Checked Out" && SearchBox.Text in SerialNumber)

  What is wrong?

Prompt 6: final polish

Sixth and last prompt of the live demo. Optional but useful — AI suggests a Marine Corps color palette so the app stops looking like a generic Power Apps default.

Use on Module 2 Prompt 6 slide Prompt 6: final polish (3 min)
Cue line for the room: “Prompt 6 in chat. Last one. Even aesthetics can be AI-guided when you give it constraints.” 
Give me a professional color scheme for a Marine Corps app: background, buttons, header. Use red and gold accents on dark background.

Debugging prompt template

Drop this when you say “every one of you will hit at least one error - here is the shape of the prompt that gets it diagnosed.” Students fill in the bracketed parts with their own situation.

Use on Module 3 debug slide Debugging prompt template
Cue line for the room: “Debugging template in chat. Copy it, replace the brackets with your own error and formula, paste into your AI tool.” 
I am building a [WHAT YOU ARE BUILDING] in Power Apps. I added this formula to my [WHERE - gallery, button, label]:

  [PASTE YOUR EXACT FORMULA]

  But I am getting this error: "[PASTE THE EXACT ERROR MESSAGE FROM POWER APPS]"

  The [RELEVANT COLUMN NAME] column is a [DATA TYPE: Date / Choice / Person / Number / Text] field in my SharePoint list. What is wrong and how do I fix it?

  ----

  Worked example:

  I am building a leave request tracker in Power Apps. I added this formula to my gallery:

  Filter(LeaveRequests, Status = "Pending" && RequestDate > Today())

  But I am getting this error: "The function 'Filter' has some invalid arguments."

  The RequestDate column is a Date field in my SharePoint list. What is wrong and how do I fix it?

Peer review checklist

Paste this when you pair students up for peer review. Each reviewer reads the four criteria, watches their partner demo, and marks Yes / Partially / Not Yet.

Use on Module 3 peer review slide Peer review checklist (4 criteria)
Cue line for the room: “Peer review checklist in chat. Reviewer reads it, watches the demo, marks each criterion. Builder defends each one.” 
Peer Review - Reviewer checks each item and provides feedback:

  1. Clear Problem Statement. Can the builder explain in one sentence what problem this solves?
  2. Core Function Works. Does the most basic version do what it needs to do? (Does not need to be pretty or complete.)
  3. Evidence of Iteration. Did the builder refine at least once? (Example: added a feature, improved formatting, fixed a bug)
  4. Can Explain Decisions. Can the builder explain why they made specific design choices? (Example: "I used a dropdown for status because there are only 3 options.")

  Score each criterion as:
    Yes        - meets the bar above
    Partially  - on the way there but incomplete
    Not Yet    - has not done this yet

  Reviewer protocol:
    0-2 min   instructor explains criteria, pairs assigned
    2-8 min   Partner A demos, Partner B reviews using the four criteria
    8-14 min  Partner B demos, Partner A reviews
    14-15 min full-class debrief: "What did you learn from your partner's approach?"

Decomposition worksheet

Paste at the start of the individual decomposition exercise. Students fill it in for a real problem from their own section that they will build before Course 3.

Use on Module 4 decomposition slide Decomposition worksheet (5 sections)
Cue line for the room: “Worksheet in chat. Pick a real problem from your section. Fill in all five sections. Ten minutes.” 
Decomposition Worksheet

  1. Problem Statement (one sentence):
     __________________________________________________________________

  2. Core Requirements (what must this do?):
     - 
     - 
     - 

  3. Decompose into 4-6 subtasks:

     | Subtask                          | Human Role               | AI Role             | Pattern   |
     |----------------------------------|--------------------------|---------------------|-----------|
     | Example: Define data structure   | Specify fields needed    | Suggest field types | Centaur   |
     |                                  |                          |                     |           |
     |                                  |                          |                     |           |
     |                                  |                          |                     |           |
     |                                  |                          |                     |           |

  4. Potential Frontier Issues (what might AI struggle with?):
     - Example: Integration with existing CAC-authenticated system
     - 
     - 

  5. Simplest Useful Version (what is the MVP?):
     __________________________________________________________________

  Pair-review checks (8 min):
     - Clarity:  Could someone outside your unit understand the problem statement?
     - Scope:    Is any subtask too big? Should it be broken down further?
     - Frontier: Is there an AI risk you missed (auth, data security, legacy integration)?
     - MVP:      Could the simplest useful version actually be built in 1-2 hours?