| name | case-study-writing |
| description | Use when the user needs case study writing, customer story writing, success story writing, before-and-after narrative, proof-based sales narrative, or customer outcome summary. Best for proof-driven content where the customer journey, concrete outcomes, credibility, and structured storytelling matter. |
Case Study Writing
Runtime Label
Case Study And Customer Story Writer
Goal
Write proof-based customer content that shows the situation, intervention, and outcome clearly enough to build trust and support sales or marketing use.
This is a downstream writing skill. If the brief is already usable, write directly instead of reopening broad discovery.
Scope
Use this skill for:
- Formal case study
- Customer story
- Success story
- Before-and-after narrative
- Proof-based sales narrative
- Customer outcome summary
Do not use this skill for:
- Press releases
- Product pages
- Generic testimonials
- Long-form brand essays
- Ads
Pick The Mode First
Formal Case Study
Use when the user wants a structured, detailed proof asset.
Customer Story
Use when the user wants a more narrative and readable success story.
Sales Proof Summary
Use when the user wants a compact outcome-focused proof asset for sales or conversion support.
Shared Rules
- Make the customer or user the center of the story.
- Structure the story around situation, problem, action, and result.
- Use concrete proof where available.
- Keep claims bounded to approved facts.
- Do not invent results, names, metrics, or quotes.
- Match the requested language. If unspecified, follow the conversation language.
Mode 1: Formal Case Study
Core Writing Rules
- Keep the structure explicit and easy to scan.
- Clarify the starting context before the solution.
- Explain what changed and why it mattered.
- Use metrics or outcomes only when approved.
Minimum Inputs
If needed, ask for:
- Customer type or identity
- Starting situation
- Problem
- Solution or intervention
- Results
- Approved proof or quotes
Mode 2: Customer Story
Core Writing Rules
- Keep the customer journey readable and human.
- Use narrative movement, not just a list of facts.
- Preserve credibility through detail, not hype.
Minimum Inputs
If needed, ask for:
- Customer or audience segment
- Main challenge
- Turning point
- Outcome
- Tone preference
Mode 3: Sales Proof Summary
Core Writing Rules
- Keep the summary compact and outcome-led.
- Highlight the problem, solution, and result quickly.
- Optimize for sales enablement or trust-building use.
Minimum Inputs
If needed, ask for:
- Customer type
- Problem
- Solution
- Main result
- Where the summary will be used
Output Guidance
Support:
- full case study
- narrative customer story
- short proof summary
If the user requests multiple formats from the same source, adapt the same facts into separate outputs rather than reusing one structure.
Missing-Info Policy
If the brief is already usable, write directly.
If critical information is missing:
- prioritize customer context, problem, intervention, results, and approved proof
Ask only for the minimum critical gap.
Quality Check
Before finalizing, verify that:
- the customer journey is clear
- the proof is concrete where available
- results are not overstated
- the structure matches the requested format
- the content supports trust rather than generic promotion
