Conference Session Abstract Pack

Use this skill to turn a topic, idea, draft, or talk outline into a submission-ready conference session pack.

Evidence and positioning rules

• Do not invent speaker credentials, awards, employers, clients, or events.
• Use only the speaker bio information provided by the user or available in connected sources.
• Tailor the submission to the named event, audience, track, format, and session length when supplied.
• If the event constraints are unknown, produce a flexible draft and list assumptions.

Inputs to look for

• Topic or rough idea.
• Target event or community.
• Audience level: beginner, intermediate, advanced, executive, maker, developer, architect, practitioner.
• Format: session, workshop, lightning talk, panel, keynote, theatre session.
• Desired tone: practical, provocative, technical, strategic, hands-on, story-led.
• Speaker bio or credentials.
• Character or word limits.

Workflow

1. Identify the central promise of the session.
2. Define the audience and why they should attend.
3. Create several title options with different emphasis.
4. Draft the main abstract in a clear, credible style.
5. Produce learning objectives or takeaways.
6. Add a short audience-fit note and optional speaker notes.
7. If constraints are missing, include a compact assumptions section.

Output format

# Conference session abstract pack

## Recommended title

[Title]

## Alternative titles

1. [Alternative]
2. [Alternative]
3. [Alternative]

## Abstract

[Submission-ready abstract]

## Audience

[Who this is for]

## Key takeaways

- [Takeaway]
- [Takeaway]
- [Takeaway]

## Why this session matters now

[Short positioning paragraph]

## Speaker bio

[Bio if source material is available, otherwise: "Speaker bio not supplied."]

## Optional short version

[Short abstract for tighter submission forms]

## Assumptions or gaps

- [Only include if needed]

Writing guidance

• Make the title specific, not generic.
• Show what the audience will be able to do or understand afterwards.
• Avoid hype and empty trend language.
• Use confident but evidence-led phrasing.
• Keep the abstract readable aloud.

References

This skill includes supporting reference material. Read the relevant reference file when the task needs additional structure, rubric detail, examples, or checklist support.

• references/cfp-quality-checklist.md - use this when additional structure, examples, or checks are useful for the task.

Quality checklist

Before responding, check:

• The title is memorable and relevant.
• The abstract has a clear promise.
• The takeaways are practical and distinct.
• No credentials or event details have been invented.
• The pack can be pasted into a CFP form with minimal editing.