Conference Talk Proposal & Slide Outliner

What this prompt does

This prompt takes your raw topic, expertise, and audience and produces the full submission package a CFP committee actually reads — three title variants under 60 characters, a 250-word abstract with a built-in hook, a reviewer-facing outline, target audience with explicit prerequisites, and three concrete takeaways. It does not ask you to write those pieces; it writes them for you, tuned to the format reviewers use when skimming hundreds of submissions in a single sitting.

The slide outline section is where this earns its keep. Each slide gets a title, a single key point, a visual suggestion, and 2–3 sentences of speaker notes. The template enforces a specific story arc (hook to problem to journey to solution to proof to call to action), and it bakes in audience interaction moments and a deliberately designed closing slide — the kind that ends on a quotable line rather than a thank-you screen. The opening constraint — no "My name is..." starts — forces a cold open. That single rule separates talks people remember from talks people sit through.

The third section covers the operational side: a per-section timing guide, likely hard questions with prepared answers, and a strategy for handling the "this never works in production" challenge that follows almost every developer talk. It also outputs slide design principles (minimal text, one idea per slide) so you are not making those decisions under deadline pressure.

When to use it

• You have a CFP deadline in the next week and a topic but no structured proposal yet.
• You are submitting to multiple conferences with different lengths — rerun with different [duration] and [slide_count] values.
• You want to co-present and need a draft both speakers can review before writing anything from scratch.
• You have given this talk before but need a fresh angle; use [unique_angle] to differentiate from your previous version.
• You are a first-time speaker who knows the technical content but has never written a talk proposal before.

Example output

For input: Laravel security, DevOps/security conference, 40 minutes, senior backend developers.

Title options:
1. "Laravel Auth Isn't Enough: Real-World Breach Patterns"  (53 chars)
2. "The Middleware You're Missing: Laravel Security"  (48 chars)
3. "Attack Surface Audit: Hardening Laravel at Scale"  (49 chars)

Abstract (excerpt):
"Three months before launch, a client's Laravel app had passed every code
review. It was still breached in week two of production. This talk walks
through the exact vectors — misconfigured queue serialization, permissive
CORS, and a Sanctum token leaked via debug logs — that reviews miss and
scanners don't catch..."

Prerequisites: Familiarity with Laravel middleware and basic HTTP security
concepts. No pentest experience required.

Slide 4 — "The Breach Timeline"
Key point: Show the 72-hour window between deploy and first exfiltration.
Visual: Annotated server log with timestamps highlighted in red.
Speaker notes: Walk through each log line slowly. Pause after the
exfiltration entry. Silence is more effective than commentary here —
let it land before advancing.

Audience interaction: After the breach timeline, ask the room to raise
hands if their app has debug logging enabled in staging. Use the count
to set up the next section.

Pro tips

• Set [unique_angle] to something falsifiable — "I ran this in production for 18 months" beats "fresh perspective on X." CFP reviewers can detect a vague angle in two sentences. If you are unsure of your angle, describe what you know that most people at this conference do not.
• If your talk is under 30 minutes, reduce [demo_count] to 1. Live demos in short slots almost always run over and kill your closing, which is the slide reviewers remember.
• Use the "likely audience questions" output to prepare your Q&A, not just the talk itself. Read the hard ones aloud the night before — the production-incident pushback especially sounds different spoken than it reads on screen.
• Run the prompt twice with different [audience] values — a DevOps crowd and a developer crowd need different abstracts even for the same topic. The 250-word limit forces real prioritization and the two versions will diverge more than you expect.
• Paste the generated speaker bio into your conference profile and then edit it. It is faster than writing from scratch, and reading a generated version surfaces positioning choices you would have glossed over if you wrote it yourself.