agentsclimarketplace
Sign in

Case study story map

Skill jpoindexter/design-case-study-skills/skills/case-study-story-map

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.From its SKILL.md

Install
npx -y skills add jpoindexter/design-case-study-skills --skill case-study-story-map

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 285 tokens by cl100k_base, as published. Nobody here has run it

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

  1. Extract the protagonist, starting state, goal, trigger, constraints, actions, pivotal decision, changed state, and outcome evidence.
  2. Arrange evidence on the eight-part Outcome Arc.
  3. Identify the actual climax: the moment value or learning becomes visible, not the launch date.
  4. Find cliffhangers: drop-offs, unresolved errors, abandoned paths, missing measurements, or outcomes without causes.
  5. Test the arc against qualitative and quantitative evidence.
  6. Collapse process steps that do not change the decision or outcome.
  7. 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:

  1. a one-sentence case-study thesis;
  2. the eight-part Outcome Arc;
  3. the three strongest evidence anchors;
  4. the pivotal decision;
  5. unresolved evidence or cliffhangers;
  6. recommended section headings.

What ships with it: 2 files

3.4 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.