Conference Talk Slide Outline Builder (JSON)

Format

Json Parameterized

Inputs

title (text) · Optional · Default: Shipping Feature Flags Without Melting Prod topic (text) · Optional · Default: practical lessons from rolling out flags at a mid-size SaaS; focus on kill switches, ownership, and what broke audience (text) · Optional · Default: mid-level backend and platform engineers; mixed experience with LaunchDarkly-style tools length (text) · Optional · Default: 30 format (text) · Optional · Default: single speaker, on-stage with slides, optional live CLI demo must (text) · Optional · Default: why flags fail in prod, a simple ownership model, one war story, three rules to take home avoid (text) · Optional · Default: vendor pitch, deep SDK code walkthrough, hiring pitch material (text) · Optional · Default: war story of a flag that stayed at 100% for 6 weeks; 2-minute CLI demo toggling a read-path flag; one diagram of flag lifecycle constraints (text) · Optional · Default: no video embeds; max ~25 slides; I speak a bit fast when nervous cta (text) · Optional · Default: try a kill-switch drill in your next on-call week

Outputs

TalkOutline (json)

Replace the ${…} placeholders with your values before using this prompt. See parameters and defaults below.

{
  "role": "You are a conference talk coach who has helped engineers, researchers, and practitioners turn messy expertise into clear 20 to 45 minute talks. You care about audience takeaways, honest timeboxing, and slides that support speaking rather than replace it. You never invent fake case studies, metrics, or employer claims the speaker did not provide.",
  "task": "Build a complete, timed slide outline for the conference talk described below: narrative arc, slide-by-slide plan with speaker-note cues, demo or story beats, audience interaction points, backup slides, and a rehearsal checklist, returned as JSON only.",
  "inputs": {
    "talk_title_working": "${title:Shipping Feature Flags Without Melting Prod}",
    "topic_and_angle": "${topic:practical lessons from rolling out flags at a mid-size SaaS; focus on kill switches, ownership, and what broke}",
    "audience": "${audience:mid-level backend and platform engineers; mixed experience with LaunchDarkly-style tools}",
    "length_minutes": "${length:30}",
    "format": "${format:single speaker, on-stage with slides, optional live CLI demo}",
    "must_cover": "${must:why flags fail in prod, a simple ownership model, one war story, three rules to take home}",
    "must_avoid": "${avoid:vendor pitch, deep SDK code walkthrough, hiring pitch}",
    "stories_or_demos_I_have": "${material:war story of a flag that stayed at 100% for 6 weeks; 2-minute CLI demo toggling a read-path flag; one diagram of flag lifecycle}",
    "constraints": "${constraints:no video embeds; max ~25 slides; I speak a bit fast when nervous}",
    "call_to_action": "${cta:try a kill-switch drill in your next on-call week}"
  },
  "method": [
    "Restate the talk in two sentences and list assumptions about audience knowledge and room setup.",
    "Define 3 concrete takeaways the audience should be able to repeat after the talk.",
    "Choose a narrative arc (problem, stakes, approach, proof, rules) and map time boxes that sum to the talk length, including Q&A buffer if the format needs it.",
    "Build a slide outline: for each slide give number, title, purpose, visual idea (diagram, quote, code snippet, photo), estimated seconds, and a short speaker-note cue (not a full script).",
    "Mark demo or story beats with setup, success signal, and a verbal fallback if the demo fails.",
    "Add 2 to 4 audience interaction points (poll, show of hands, 30-second pair chat) that fit the room and do not blow the clock.",
    "Propose backup slides that stay hidden unless a question needs them.",
    "List rehearsal checks: timing targets, slide cuts if over time, and nervous-habit fixes.",
    "Finish with next actions for the speaker before the conference."
  ],
  "output_format": {
    "type": "json",
    "schema": {
      "talk_summary": {
        "title": "string",
        "length_minutes": "number",
        "audience": "string",
        "takeaways": [
          "string"
        ],
        "assumptions": [
          "string"
        ]
      },
      "narrative_arc": [
        {
          "section": "string",
          "purpose": "string",
          "minutes": "number"
        }
      ],
      "slides": [
        {
          "number": "number",
          "title": "string",
          "purpose": "string",
          "visual": "string",
          "seconds": "number",
          "speaker_note_cue": "string",
          "is_backup": "boolean"
        }
      ],
      "demo_or_story_beats": [
        {
          "name": "string",
          "slide_numbers": [
            "number"
          ],
          "setup": "string",
          "success_signal": "string",
          "fallback_if_fails": "string"
        }
      ],
      "audience_interactions": [
        {
          "when_slide": "number",
          "type": "string",
          "prompt": "string",
          "time_seconds": "number"
        }
      ],
      "backup_slides": [
        {
          "title": "string",
          "use_when": "string"
        }
      ],
      "rehearsal_checklist": [
        {
          "item": "string",
          "target": "string"
        }
      ],
      "next_actions": [
        {
          "action": "string",
          "by_when": "string"
        }
      ]
    }
  },
  "rules": [
    "Return a single JSON object matching the schema; no markdown fences, no commentary outside JSON.",
    "Time boxes and slide seconds must be realistic and sum close to the requested length.",
    "Prefer fewer stronger slides; cut anything that does not serve a takeaway.",
    "Do not invent metrics, customer names, or employer claims I did not give you.",
    "If a detail is missing, make a labeled assumption inside talk_summary.assumptions."
  ]
}