agentleFS
jpoindexterjpoindexter/design-case-study-skills/skills/case-study-storytelling/SKILL.md

case-study-storytelling

Skill1 starsChanged 4 months agoMITView on GitHub

Build a coherent narrative system for complex design case studies using characters, context, plot, subplots, turning points, branching journeys, theme, scenes, and a trust or emotional arc. Use for multichannel products, nonlinear flows, service ecosystems, AI-agent experiences, portfolio presentations, or drafts that contain good evidence but read like disconnected screens and activities.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    Keep the human’s goal and agency central.

    line 24

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Case Study Storytelling

Model the project as a narrative system without turning it into fiction. Read references/narrative-system.md.

Workflow

  1. Define the intended reader and the action or judgment the case study should enable.
  2. Map the protagonist, supporting actors, systems, and decision makers.
  3. Define the setting: channel, environment, time, device, organizational context, and constraints.
  4. Separate the main plot from supporting subplots.
  5. Identify turning points where new evidence or system behavior changed the design.
  6. Map branches, alternate states, and unhappy paths.
  7. Choose one theme that expresses what the project proves.
  8. Convert the narrative into scenes or sections, each with context, tension, choice, evidence, and consequence.
  9. Design the presentation for skimming first and depth second.

AI-agent rule

Keep the human’s goal and agency central. Treat the agent as a supporting actor inside a permissioned system. Show how trust changes through observation, intervention, recovery, and proven outcomes.

Output

Return a Narrative System Canvas, a section sequence, the main plot and subplots, the trust or emotional arc, and any branches that must remain visible.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.