case-study-story-map
Skill1 starsChanged 4 months agoMITView on GitHub
Map project evidence into a user-centered outcome arc for a product or design case study. Use when raw notes are chronological, the story lacks tension or a clear result, the product or designer has become the hero instead of the user, a journey needs a beginning-middle-end structure, or research and analytics must be connected to goals, conflicts, pivotal decisions, and measurable outcomes.
In this repository11 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Test the arc against qualitative and quantitative evidence.
- Distinctive: line 24
Use conflict to explain real constraints, not manufacture theater.
- Distinctive: line 25
Keep project chronology subordinate to causal logic.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Case Study Story Map
Turn evidence into an outcome arc. The user or operator is the protagonist; the product, designer, and AI agent are supporting forces.
Read references/outcome-arc.md.
Workflow
- Extract the protagonist, starting state, goal, trigger, constraints, actions, pivotal decision, changed state, and outcome evidence.
- Arrange evidence on the eight-part Outcome Arc.
- Identify the actual climax: the moment value or learning becomes visible, not the launch date.
- Find cliffhangers: drop-offs, unresolved errors, abandoned paths, missing measurements, or outcomes without causes.
- Test the arc against qualitative and quantitative evidence.
- Collapse process steps that do not change the decision or outcome.
- Draft section headings that make the arc scannable without dramatic exaggeration.
Rules
- Use conflict to explain real constraints, not manufacture theater.
- Keep project chronology subordinate to causal logic.
- Show how evidence changed the work.
- Preserve branching, failure, and iteration when the real journey was non-linear.
- Mark hypotheses and unknown causes instead of forcing a neat ending.
Output
Return:
- a one-sentence case-study thesis;
- the eight-part Outcome Arc;
- the three strongest evidence anchors;
- the pivotal decision;
- unresolved evidence or cliffhangers;
- recommended section headings.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

