Write keynotes, executive remarks, ceremonial speeches, conference openers, talking points, crisis or change-management addresses, and spoken rewrites that sound credible aloud, fit the speaker, and move the room under live-delivery constraints. Use when work needs speech structure, audience-sensitive rhetoric, cadence polish, line-by-line speakability fixes, or talking-point systems for real people speaking live. Do not use for generic article ghostwriting, debate-prep war gaming, teleprompter logistics, or broad communications strategy beyond the speech itself.
Write for the ear, the room, and the speaker’s actual mouth.
Use this skill to draft or repair spoken communication that must land live. Focus on audience stakes, speaker credibility, structure under time pressure, line-level speakability, emotional control, and memorable phrasing that survives delivery.
Produce outputs such as:
The work should sound sayable and situationally intelligent, not just polished on the page.
Define the occasion, what just happened, what the audience is carrying into the room, and what needs to change by the end. A speech is a live intervention, not a formatted essay.
Match vocabulary, confidence level, humor, sentence length, and emotional range to the actual speaker. A line that sounds impressive but unbelievable in their voice is a bad line.
Open quickly, earn attention, orient the room, develop a few clear beats, and land cleanly. Too many ideas flatten impact. Most speeches improve when narrowed.
Favor shorter sentences, strong verbs, concrete nouns, strategic repetition, and transitions the speaker can carry under pressure. Readability is not enough; the line must be breathable.
In high-stakes settings, warmth, grief, pride, apology, and conviction should feel earned. Specificity beats melodrama. Restraint often sounds more truthful than intensity.
Cut jargon, throat-clearing, stacked subordinate clauses, numbers overload, and page-only elegance. Mark likely stumble points and simplify them.
Calibrate length to real speaking pace. Build in anchors: a repeatable phrase, a clear contrast, a callback, a crisp ask, or three memorable beats the audience can retain.
Collect as many of these as possible:
If evidence is thin, state assumptions instead of inventing biography, sentiment, or audience reaction.
Prefer:
Avoid:
Use adjacent skills when the center of gravity shifts:
Before finishing, confirm that the output:
Use prompt.md for delivery stance and answer structure.
Use examples/README.md for deliverable shapes.
Use guides/qa-checklist.md before finalizing.
Use meta/skill.json for metadata, boundaries, and typical IO.