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)