talk · diff
git:20260810.4e6ccee to git:20261007.7f41b57
34 added, 87 removed. Audit A to A.
---
name: talk
- description: >-
- Conference talk builder for technical CFP submissions, speaking proposals, timed talk outlines,
- and slide flows. Use when the user asks for a conference talk, CFP abstract, talk proposal, or to
- turn a project/article into a speaking proposal.
+ description: Build a technical conference proposal, audience promise, timed outline, and slide flow from the speaker's real evidence.
disable-model-invocation: true
argument-hint: "[conference topic or title]"
---
- # Conference Talk Builder
-
- Structured for technical developer conferences. Produces three core deliverables: CFP abstract, talk
- outline with timing, and key slides list. Optional iA Presenter markdown is generated only when the
- user asks for slide markdown.
-
- ## What Makes a Talk Work
-
- The talk structure that gets accepted and remembered:
-
- 1. **Visceral opening** — a failure story, a question the audience can't answer, or a stat that
- reframes the topic. Not "today I'm going to tell you about X."
- 2. **The painful thing everyone does** — establish shared experience. The audience needs to
- recognize themselves.
- 3. **The journey with failed attempts** — what the speaker tried, what failed, and what changed.
- This is credibility: lived experience, not a literature review.
- 4. **The insight with a demo** — the thing attendees came for. Keep demos minimal and have a backup.
- 5. **Monday morning takeaways** — 3 concrete actions attendees can take back to work.
-
- ## Workflow
-
- ### 1. Clarify the Submission
-
- Before drafting, confirm or explicitly mark assumptions for:
+ # Conference talk builder
- - target conference and audience level
- - talk length (default: 25–30 minutes)
- - one-sentence core insight
- - speaker's direct experience with the topic
+ Produce a submission and talk shape that match the target event. Conference requirements outrank default lengths and sections.
- Do not invent speaker experience. If credibility is missing, ask for the story, project, production
- incident, research, or client work that gives the speaker standing.
+ ## 1. Establish the brief
- Complete when those four inputs are known or a clearly labeled assumption is shown for user approval.
+ Gather or label assumptions for:
- ### 2. Draft CFP Abstract
+ - conference, submission fields, and deadlines
+ - audience and expected prior knowledge
+ - talk format and duration
+ - one-sentence audience change
+ - the speaker's direct evidence or experience
- **Format (400–500 words total):**
+ Use the event's current CFP requirements when available. Keep invented experience, incidents, results, and credentials out of the proposal.
- ```text
- TITLE
- [Direct and specific. Concrete beats clever.]
+ Complete when every required submission field and the speaker's evidence base are known or visibly unresolved.
- ABSTRACT (250–300 words)
- Paragraph 1: The problem — what's painful now and why it matters
- Paragraph 2: The journey — what was tried, what failed, what changed
- Paragraph 3: What attendees will leave able to do
+ ## 2. Form the promise
- WHAT ATTENDEES WILL LEARN
- - [Specific skill or decision they'll be able to make]
- - [Specific tool, pattern, or technique they'll use]
- - [Mental model that changes how they approach this problem]
+ State:
- SPEAKER BIO HOOK (50 words)
- One sentence about why this speaker is the right person for this topic.
- ```
+ > After this talk, [audience] can [specific action or decision] because they understand [core insight].
- Complete when the abstract names the problem, journey, takeaway, and credibility hook.
+ Complete when the promise is achievable in the available time and supported by the speaker's evidence.
- ### 3. Build the Timed Outline
+ ## 3. Draft the proposal
- ```text
- [0:00-2:00] Opening hook — failure/question/stat
- [2:00-7:00] Problem setup — the painful thing everyone does
- [7:00-15:00] Journey — failed attempts and turning point
- [15:00-22:00] Resolution — insight, demo, or concrete example
- [22:00-25:00] Takeaways + Q&A setup
- ```
+ Follow the event's fields and limits. A typical proposal needs:
- Adjust for actual length. Keep demo segments to 5–7 minutes max.
+ - direct title
+ - problem and stakes
+ - distinctive insight or journey
+ - concrete attendee outcomes
+ - credibility grounded in real work
- ### 4. List Key Slides
+ Complete when a reviewer can identify audience fit, novelty, evidence, and attendee value without reading the outline.
- Not the slides themselves — the logical flow. One line per slide/beat:
+ ## 4. Build the timed outline
- ```text
- 1. Opening image/question
- 2. The mistake everyone makes
- 3. Concrete wrong-way example
- 4. Moment of discovery
- 5. Key concept / architecture diagram
- 6. Right-way example
- 7. Proof: benchmark, result, or production lesson
- 8. Demo or backup screenshot
- 9. Three takeaways
- 10. One slide people will photograph
- ```
+ Budget every major beat, including transitions, demonstrations, takeaways, and Q&A when required. Load `references/story-circle.md` when failed attempts or changed practice provide the narrative spine.
- ### 5. Generate iA Presenter Markdown Only If Requested
+ A demonstration needs a bounded purpose and a tested fallback such as captured output or screenshots.
- If the user asks for slide markdown, load `references/ia-presenter-syntax.md` and follow it. Do not
- reconstruct the syntax from memory.
+ Complete when segment durations sum to the actual slot and the audience promise is demonstrated before the close.
- ## Output
+ ## 5. Build the slide flow
- Deliverables in this order:
+ List one audience job per slide or beat. Mark diagrams, code, demos, evidence, and the final photographed takeaway. Generate slide Markdown only when requested; then load `references/ia-presenter-syntax.md` and validate the rendered deck.
- 1. CFP abstract
- 2. Talk outline with timing
- 3. Key slides list
- 4. iA Presenter markdown, only if requested
+ ## Completion gate
- Present 1–3 together; they inform each other and a CFP reviewer needs the full shape.
+ Deliver the requested proposal fields, timed outline, and slide flow. State assumptions, source evidence, timing total, demo fallback, and any event requirement that remains unverified.
## References
| Priority | Load when | Reference |
| --- | --- | --- |
- | 1 | Building the narrative arc or structuring the talk story | `references/story-circle.md` |
- | 2 | Generating iA Presenter slide markdown | `references/ia-presenter-syntax.md` |
+ | 1 | Tension, failed attempts, discovery, or transformation carries the talk | `references/story-circle.md` |
+ | 2 | Generating iA Presenter slide Markdown | `references/ia-presenter-syntax.md` |