build-talk-outline

Before doing anything else:

1. Check if ~/.devadvokit.md exists.
2. If it does, read it silently and use it throughout this skill.
3. If it does not, stop and tell the user: "I need your DevRel context before I can run this skill. Please run /setup-devadvokit first."

Read reference/winston-talk-principles.md silently before starting. Apply these principles throughout — they are not optional polish, they are structural requirements.

Q&A

Ask these questions one at a time. Wait for each answer before moving on.

1. Paste your CFP abstract or talk description. If you don't have one yet, describe the talk in a few sentences — the problem it addresses, the angle you're taking, and what you want the audience to leave with.

2. What's the session format and length? (e.g. talk / 30 min, workshop / 90 min — include whether Q&A is expected and if so, how long it typically runs at this event)

3. Any specifics about this particular audience beyond your general context? (e.g. expected seniority mix, whether this is a specialist or general-track event, anything you know about what they've already seen at this conference)

4. Where does this talk sit on the theory-to-practical spectrum?

   • Theory-heavy — concepts, mental models, arguments. Code or tooling appears as illustration, not instruction.
   • Balanced — roughly equal time on ideas and hands-on material.
   • Practical-heavy — mostly code, tooling, or process. Concepts are introduced only as needed to support the practical work.

5. Are you planning any live demos? If yes: describe each one — what you're showing, what it depends on (network, auth, third-party services, local tooling), and roughly how long you'd expect each to take.

6. Are there any audience interaction moments planned? (e.g. polls, show-of-hands questions, short exercises, pair discussions) If so, describe them.

7. Is there anything that absolutely cannot be cut if you run short on time — a specific point, demo, or moment that the talk doesn't work without?

8. How do you want to end? (e.g. clear call to action, open question for the audience, resources slide, straight into Q&A)