Load Context First

Before executing this skill, read the following files from the project folder if they exist:

1. USER.md — who the user is, how they think, how they work
2. BUSINESS.md — their business, products, positioning, brand voice, content strategy
3. ICP.md — their ideal customer, their language, their fears, what makes them buy
4. Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
5. Any additional context provided by the user in this session

Use all context silently. Do not reference or summarize files unless asked.

Case Study Newsletter

Purpose: Write a newsletter (600-1,000 words) that breaks down a real result into an engaging, educational case study. Readers learn from the breakdown AND see the writer's credibility demonstrated through real outcomes.

When to Activate

Use this skill when:

• User wants to share a client win or personal result
• User mentions "case study", "breakdown", "how I did X", or "results"
• User has specific numbers/outcomes they want to turn into content
• User wants to demonstrate credibility through real examples

Why Case Studies Work

Case studies are the most credible content format because:

• Proof over promises — you're showing, not claiming
• Education through example — readers learn by seeing the process
• Builds trust — real numbers and real situations build authority
• Attracts similar clients — your ideal customer sees themselves in the case study

Required Input

Ask the user for (if not provided):

• The situation/context — Who was the client or what was the starting point?
• The problem — What challenge needed solving?
• What was done — What specific actions were taken?
• The results — What happened? Numbers, metrics, outcomes.
• Why it worked — What was the insight or principle behind the success?

If writing about a client: Ask if client details should be anonymized or named.

Structure

Section 1: The Hook (50-100 words)

Open with the result. Lead with the most impressive number or outcome.

Patterns:

• "[Metric] in [timeframe]. Here's the breakdown."
• "A [type of client] came to me with [problem]. [X time] later, [result]."
• "What happens when you [action]? [Result]. Here's exactly how."

Rules:

• Start with the result, not the backstory
• Be specific — numbers, timeframes, concrete outcomes
• Create curiosity about the HOW

Section 2: The Situation (100-150 words)

Set the scene. Help readers understand the starting point so they can see themselves in the story.

Include:

• Who (anonymized if needed — "a B2B SaaS founder" or "a freelance designer")
• Where they were — the specific challenge or pain point
• What they'd already tried (optional but powerful — shows this wasn't the obvious solution)
• Why this matters — connect it to a common problem your audience faces

Rules:

• Keep it relatable — readers should think "that sounds like me"
• Don't over-dramatize — let the facts speak
• Be specific enough to be credible, vague enough to protect privacy if needed

Section 3: What Was Done (200-350 words)

The tactical meat. Walk through the specific approach, step by step.

Format options:

• Numbered steps (for sequential processes)
• Bulleted phases (for parallel work streams)
• Narrative walkthrough (for more complex situations)

For each action/step include:

1. What was done (specific action)
2. Why it was chosen (the reasoning)
3. How it was executed (enough detail to be useful)

Rules:

• Be specific enough that someone could replicate the approach
• Include the reasoning behind decisions, not just the decisions
• Mention tools, frameworks, or methods used
• Don't gatekeep — give real, actionable detail

Section 4: The Results (100-150 words)

Present the outcomes clearly and specifically.

Format:

• Lead with the headline metric
• Include 2-4 supporting metrics or qualitative outcomes
• Show the before → after comparison
• Include the timeframe

Example structure:

The results after [timeframe]:

• [Primary metric]: [before] → [after]
• [Qualitative outcome]: [what changed]

Rules:

• Use real numbers (or reasonable approximations if client-approved)
• Don't inflate or exaggerate
• Include timeframe — results without context are meaningless
• If results are ongoing, say so

Section 5: Why It Worked (100-150 words)

Extract the principle behind the success. This is what makes the case study educational, not just a brag.

Include:

• The core insight or principle that drove the result
• Why this approach worked when others didn't
• The transferable lesson (what applies beyond this specific case)

Rules:

• One key principle, not five
• Make it applicable to the reader's situation
• Connect it back to a broader truth in your niche

Section 6: What You Can Steal (100-150 words)

Close with 3-5 actionable takeaways the reader can apply immediately.

Format:

What you can steal from this:

1. [Specific, actionable takeaway]
2. [Specific, actionable takeaway]
3. [Specific, actionable takeaway]

Rules:

• Each takeaway should be doable this week
• Frame them as instructions, not observations
• Connect each one back to the case study evidence

Subject Lines

Generate 5 options:

1. Results-first: "How [action] led to [result] in [timeframe]"
2. Breakdown format: "Breaking down: [impressive result]"
3. The how: "How I helped [who] achieve [what]"
4. Numbers-first: "[Number] [metric] from [single action]"
5. Curiosity: "The [counterintuitive thing] that produced [result]"

Output Format

## Subject Line Options

1. [Option 1]
2. [Option 2]
3. [Option 3]
4. [Option 4]
5. [Option 5]

**Recommended**: Option [X] — [reasoning]

---

## Newsletter: [Chosen Subject Line]

**Word count**: ~[X] words

---

[Hook — lead with the result, 50-100 words]

### The Situation
[Context and starting point, 100-150 words]

### What Was Done
[Step-by-step breakdown, 200-350 words]

### The Results
[Clear metrics and outcomes, 100-150 words]

### Why It Worked
[Core principle, 100-150 words]

### What You Can Steal
[3-5 actionable takeaways, 100-150 words]

---

**Stats**: [X] words | [X] steps detailed | [X] takeaways

Quality Checklist

• Opens with the result (not the backstory)
• Situation is relatable — reader can see themselves
• Actions are specific enough to be useful
• Results include real numbers and timeframes
• "Why It Worked" extracts a transferable principle
• Closes with actionable takeaways
• 600-1,000 words total
• No fabricated numbers or results
• Client privacy respected (anonymized if needed)
• Voice matches context profiles