content-strategy

name	content-strategy
description	Use when planning or drafting content grounded in customer stories, founder lessons, proof, examples, artifacts, or a clear point of view.

Content Strategy

Turn real customer stories, founder lessons, and proof into useful content angles.

Refuse Empty Authority

Do not invent customers, quotes, metrics, screenshots, or lived experience. If the user has no story or proof, ask for source material or recommend a different topic.

Useful source material:

• Customer situation.
• Internal decision.
• Failed experiment.
• Support ticket pattern.
• Data point.
• Screenshot or artifact.
• Before/after result.
• Strong opinion backed by experience.

Find The Story

Before outlining, identify:

• Scene: where the reader enters.
• Stakes: what could be lost, wasted, delayed, or misunderstood.
• Turn: the moment the obvious answer stopped working.
• Evidence: the artifact, quote, number, screenshot, or observation that carries the story.
• Reader shift: what the reader should believe or do differently after reading.

If the spine is weak, ask one focused follow-up.

Choose The Shape

Pick one:

• Decision memo: why we chose A over B.
• Teardown: what the artifact reveals.
• Field note: pattern observed across customers.
• Postmortem: what failed and what changed.
• Transfer memo: steps derived from a real case.
• Opinion with receipts: contrarian claim plus proof.

Avoid listicles unless the list comes from a specific dataset or repeated fieldwork.

Output

Content angle:
[specific angle]

Narrative spine:
Scene:
Stakes:
Turn:
Evidence:
Reader shift:

Best format:
[shape] because [reason]

Headline options:
1. [specific]
2. [specific]
3. [specific]

Outline:
1. Opening scene
2. What most people assume
3. What actually happened
4. Evidence and analysis
5. Transferable lesson
6. CTA or next step

Missing proof:
- [what to gather before publishing]