50 slides: an untimed welcome, a 50-minute main story, a separate 6-minute product section and an 18-minute technical module. Use Overview to choose a section.
Story: meet the system → learn the method → make context durable → scale responsibly → test value → adopt selectively.
| Time | Slide | Delivery action |
|---|
| Untimed | 1 · The portal is open. | Let the room settle. Use fullscreen if presenting. Choose Begin when you are ready. |
| 00:00–01:00 | 2 · We had a plan. The AI had other plans. | Pause for hands. Let the dashboard-to-platform joke land. Introduce yourself in one sentence. |
| 01:00–02:30 | 3 · Here’s the whole system. | Trace client → method → project records → next task. Mention the team pack and platform boundary; save detailed paths for later. |
| 02:30–03:30 | 4 · Six parts. One working system. | Use one short sentence per part. Explain that an agent role is a job description and a hook reacts to an event. |
| 03:30–04:30 | 5 · Four client families. One shared method. | Name four families, then CLI / desktop / IDE / cloud. Explain the evidence ladder once. |
| 04:30–05:00 | 6 · No single harness. No magic ring. | Keep this to thirty seconds. Describe complementary jobs, not a feature comparison. |
| 05:00–06:30 | 7 · A fresh session. A new window. | Click Three hours later. Define agent, context and session; keep the invented counts illustrative. |
| 06:30–07:30 | 8 · What. How. Why. Then make it compound. | Point once to each word; explain compounding with the return arrow. |
| 07:30–09:30 | 9 · Agree the work. Then build the work. | Trace understand → agree → build → review → capture. Click PLAN and REVIEW; do not recite nine definitions. |
| 09:30–10:30 | 10 · Nine steps for a typo? | Show hotfix and research. Use the full-cycle row to contrast a feature. Do not improvise routing predictions. |
| 10:30–11:30 | 11 · Your fifth dashboard should remember the first. | Click Package the pattern once. Mention empty states and export consistency. |
| 11:30–13:30 | 12 · Small steps. A coherent piece of work. | Walk T01–T03 as one package. Explain the defect when CSV and screen filters differ. |
| 13:30–16:00 | 13 · “Looks good” is not a review. | Trace the cancellation question through evidence to decision. Distinguish executed from traced evidence. |
| 16:00–18:00 | 14 · A profile should change the work. | Toggle Lab → Customer pilot. Read the changed evidence field. |
| 18:00–19:30 | 15 · Your setup. Your project’s memory. | Trace left → right, then the Git arrow. Point to the dashed runtime box last. |
| 19:30–21:00 | 16 · The work leaves a way back. | Click through the three example steps: clarification, saved decision, fresh session. Explain who asks and who writes. Keep the registered-hook lane separate. |
| 21:00–23:00 | 17 · Delete the chat. Keep the plot. | Trace the four committed pointers to T002. The saved helper checks the map. |
| 23:00–25:30 | 18 · A lesson that never returns is just a diary entry. | Click Before → Fixed → Reintroduce bug. Read the red result aloud. |
| 25:30–26:30 | 19 · Correct once. Make the correction travel. | Explain the different jobs of a lesson, ADR, skill and test. |
| 26:30–29:00 | 20 · Parallel work. One accountable plan. | Trace task map → independent writer lanes → lane reviews → integrated review. Use report remediation as the example. |
| 29:00–31:00 | 21 · Same question. More than one perspective. | Trace one frozen packet into separate contexts and evidence-based synthesis. Point to the incomplete slot. |
| 31:00–31:30 | 22 · I stopped being the queue. | Point to 55. Click “Then I turned on swarming.” Let 711 land in silence for two beats. Point to the original screenshots, then trace the report-to-fix flow. Use “Replay reveal” if rehearsing. |
| 31:30–32:00 | 23 · We broke GitHub.* | Point to the unresponsive-tab message, pause for the joke, then move on. Do not open the enormous PR live. |
| 32:00–33:00 | 24 · Markdown can tell you to lock it. It cannot be the lock. | Point to both objects; name permissions and CI as examples. |
| 33:00–34:30 | 25 · Same kitchen. Three ways to build. | Show three arms and the frozen brief. State results are pending before describing expected value. |
| 34:30–36:30 | 26 · A receipt beats a pretty screenshot. | Walk the three actions. Use the guide until actual accepted candidates exist. Never substitute the reference solution for an arm. |
| 36:30–38:00 | 27 · Four measures. Zero invented winners. | Read the measures. Explain one confound and why failures stay in the result set. |
| 38:00–39:00 | 28 · A smarter model still wasn’t in last week’s meeting. | Use the rejected-option example. Intelligence cannot replace unavailable project knowledge. |
| 39:00–40:00 | 29 · 96 skills. A smaller working set. | Name three consolidated methods; do not read the catalog. |
| 40:00–41:30 | 30 · Different roles. Shared context. | Give one concrete benefit each for demo builder, architect and developer. |
| 41:30–43:30 | 31 · Don’t roll out a philosophy. Run a small experiment. | Point at the four measurements on screen. Keep “what would make us stop?” rhetorical — the discussion is next. |
| 43:30–49:00 | 32 · What are you tired of explaining twice? | Take a remote participant first. Choose one task, one recurring failure and what should remember it. |
| 49:00–49:30 | 33 · The talk ends. The toolkit stays. | Name the four deliverables. Explain Core as the small, explicit workflow shell for a customer case. Point attendees to the public site. |
| 49:30–50:00 | 34 · Keep the creativity. Stop paying twice. | Do not read the rows; give today’s example for each: the 09:12 agreement, the rejected option B, the tenant leak. Pause. End on time. |