The output of this skill. Every field must be something that changes how content gets made — if it wouldn't change a post, it doesn't belong. Keep it tight; the content skills read it constantly.
Copy everything below the line into audience.md and fill it in.
# Audience — {Business or Client Name}
<!-- version: 1.0 · updated: {date} · derived from: brand-profile v{n} · evidence: {sources used / "limited — assumptions flagged"} -->
## Primary segment: {label}
> The one that moves the business most right now. Build for them first.
## Segment 1 — {short label} ⭐ primary
- **Who (relevant traits only):** {role/identity that actually changes the content}
- **Buyer vs follower:** {same person? or buyer = X, follower/champion = Y}
- **Jobs-to-be-done:**
- Functional: {the practical progress}
- Emotional: {how they want to feel}
- Social: {how they want to be seen}
- **Pains:** {what blocks the job / hurts now}
- **Desires:** {the outcome they want}
- **Beliefs:** {what they currently think — to meet or challenge}
- **Objections:** {why they hesitate — content should answer these}
- **Language bank (their words):**
- Problem: "{verbatim}", "{verbatim}"
- Desire: "{verbatim}"
- Objection: "{verbatim}"
- They call it: "{their term}" (not "{our jargon}")
- **Where they are:** {platforms + mindset on each}
- **Who/what they follow & engage with:** {accounts, creators, formats}
- **Sophistication:** {beginner ↔ expert — sets vocabulary/depth}
- **Transformation (before → after):** {the shift the brand enables}
## Segment 2 — {label} (optional)
- {same fields}
## Segment 3 — {label} (optional)
- {same fields}
## Notes
- {multi-audience notes, aspirational vs current, evidence gaps to validate}
How downstream skills read this
content-pillarsturns the jobs and pains into ownable, audience-relevant pillars.batch-content-planuses segments, pains, and objections to assign goals and angles.hook-writer/caption-writerpull hooks, pains, and CTAs from the language bank so copy mirrors the audience's own words.- Treat the language bank and jobs-to-be-done as the highest-signal sections.
If a segment's fields are thin or marked "(assumed)", write conservatively and prioritize validating them with real evidence.
