---
name: speaker-content-processor
description: Process and transform speaker content for various event contexts. Use when creating bios in multiple formats, writing session descriptions, drafting CFP submissions, generating speaker proposals, or processing speaker packets. Triggers on requests involving speaker bios, session descriptions, learning outcomes, CFP submissions, or speaker proposals.
---

# Speaker Content Processor

Transform speaker content into professional, event-ready formats across bios, session descriptions, proposals, and speaker packets.

## Quick Reference

### Bio Formats
- **50-word** (program book): Name + expertise + achievement + humanizing detail
- **100-word** (website): Expanded with 2-3 credentials, professional-approachable tone
- **25-word** emcee intro: "Please welcome [Name], [credential] who [achievement]."

### Session Description Formula
1. Opening hook - what's at stake (15 words)
2. What attendees will learn/do (30 words)
3. Takeaways they'll leave with (20 words)
4. Why it matters now (10 words)

### Learning Outcomes
Start each with action verbs: Implement, Apply, Build, Create, Deploy, Evaluate, Identify, Master
Never use: Explore, Discuss, Learn about, Understand, Discover

---

## Workflow by Task

### Task 1: Generate Bio Variations
1. Load `references/bio-formats.md`
2. Extract key facts: name, title, credentials, achievements, personal detail
3. Remove banned words/phrases
4. Generate all three formats (50-word, 100-word, emcee intro)
5. Ensure third-person consistency throughout

### Task 2: Create Session Description
1. Load `references/session-standards.md`
2. Identify core value proposition and attendee benefit
3. Rewrite in attendee-focused language (not speaker-centered)
4. Generate 75-word abstract + 3 action-verb takeaways
5. Verify no weak verbs ("explore," "discuss," "dive into")

### Task 3: Draft CFP Submission
1. Load `references/proposal-templates.md` and `references/session-standards.md`
2. Match template to CFP requirements
3. Ensure track alignment is explicit
4. Generate all required elements: title, description, outcomes, bio, tech requirements
5. Verify word counts match requirements exactly

### Task 4: Create Speaker Proposal
1. Load `references/proposal-templates.md` and `references/value-framework.md`
2. Choose appropriate template (direct client, bundle, bureau)
3. Customize for recipient's specific context/needs
4. Include clear scope, investment, and next steps
5. Add non-cash considerations if budget-sensitive

### Task 5: Process Speaker Packet
1. Load `references/packet-processing.md`
2. Review all submitted materials
3. Generate standardized outputs (bios, abstract, takeaways, alt text)
4. Run quality control checklist
5. Export in markdown table format for event systems

---

## Key Principles

### Attendee-Focused Language
- FROM: "In this session, I'll share my experience..."
- TO: "Walk away with a tested framework for..."

The shift: What attendees GAIN, not what speaker will SHARE.

### Active Voice, Action Verbs
Every learning outcome starts with: Implement, Apply, Build, Create, Deploy, Evaluate, Identify, Master

Never: Explore, Discuss, Learn about, Understand, Discover, Dive into, Unpack

### Remove Fluff
Banned words: thought leader, visionary, guru, passionate about, world-class, cutting-edge, revolutionary, groundbreaking, leverage, synergize

Replace with: specific numbers, named clients/events, measurable outcomes, concrete credentials.

### Speakable Intros
Test emcee introductions by reading aloud. No awkward phrases, no tongue-twisters, builds anticipation.

---

## Resources

- `references/bio-formats.md` - Bio length standards and format templates
- `references/session-standards.md` - Session descriptions, learning outcomes, CFP checklist
- `references/value-framework.md` - Pricing, scope definitions, partnership language
- `references/proposal-templates.md` - CFP, client, bundle, and bureau templates
- `references/packet-processing.md` - Processing workflow and export formats