Skip to content
Back to search

case-study-storytelling

Evidence-led product design case study storytelling skill

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mengxuebi-mush--case-study-storytelling/badge.svg)](/listings/mengxuebi-mush--case-study-storytelling)

HTML

<a href="/listings/mengxuebi-mush--case-study-storytelling"><img src="/api/listings/mengxuebi-mush--case-study-storytelling/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install the skill from `skills/case-study-storytelling`, or copy that directory into a Codex skills directory.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 78 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Case Study Storytelling
  2. **Plan it. Tell it. Defend it.**
  3. A skill with three user-facing modes for taking a product-design case study from raw
  4. material to interview readiness.
  5. ## Choose a mode
  6. | Mode | Use it when | What it produces |
  7. |---|---|---|
  8. | `/plan` | You have a story draft, case-study webpage, or existing deck. Start here for a new story. | An evidence-led argument, narrative diagnosis, and slide-by-slide story map with artifacts and gaps. |
  9. | `/script` | The story plan is approved and the slide sequence is close to final. | Flexible slide-aligned talking points, emotional movement, causal emphasis, and natural transitions—not a verbatim script unless requested. |
  10. | `/follow-up` | The story, slides, and script are ready and you want to prepare for interviewer questions. | Questions caused by the story's visible and spoken claims, plus structured answers, drill-downs, claim boundaries, and missing facts. |
  11. ## Suggested workflow
  12. Run the modes in this order:
  13. ```text
  14. /plan → refine and approve the story → finalize the slides → /script → /follow-up
  15. ```
  16. 1. **Start with `/plan`.** Build and revise the argument, causal arc, evidence, gaps,
  17. artifacts, and slide sequence. Do not move on while a known gap could still change
  18. the core story.
  19. 2. **Bring the slides close to final.** Stabilize the slide order, titles, primary
  20. artifacts, and important reveals or interactions. Visual polish may continue, but
  21. the presentation's meaning and sequence should no longer be moving substantially.
  22. 3. **Run `/script`.** Prepare the delivery against the real slides so every talking
  23. point, emotional turn, and transition has a stable place.
  24. 4. **Run `/follow-up`.** Prepare interviewer questions after the script so the skill can
  25. pressure-test both what appears on screen and what the presenter plans to say.
  26. During any stage, the agent may revise the current artifact in response to feedback
  27. without silently advancing to the next mode.
  28. The skill keeps story logic, delivery preparation, and interview defense connected to
  29. one truthful source. It does not invent evidence, stakes, failures, emotions, metrics,
  30. ownership, or impact.
  31. ## Install
  32. Install the skill from `skills/case-study-storytelling`, or copy that directory into a
  33. Codex skills directory.
  34. ## Use
  35. Ask your coding agents to use `case-study-storytelling` with the mode you need. For
  36. example:
  37. ```text
  38. Use $case-study-storytelling /plan on this case-study webpage.
  39. Use $case-study-storytelling /script on the approved story plan.
  40. Use $case-study-storytelling /follow-up on the final story and script to prepare for interviewer questions.
  41. ```
  42. For `/plan`, provide one or more of:
  43. - a complete story draft;
  44. - a case-study webpage;
  45. - an existing presentation deck;
  46. - optional audience context such as a job description or company notes.
  47. The planning output is a standalone HTML review file with an English / Chinese switch
  48. by default. The skill does not design or implement the final deck; a separate visual or
  49. presentation workflow can use the approved story plan.
  50. ## Optional local profile
  51. Personal installations may add
  52. `skills/case-study-storytelling/references/local-profile.md` to load a private audience
  53. lens or downstream handoff. This file is intentionally not included in the public
  54. distribution; the core workflow remains unchanged.
  55. ## License
  56. MIT. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.