case-studylisted

# `/case-study` — Client outcome case study page Documents one real client outcome end-to-end. Case studies sit at the decision stage — readers are evaluating whether the site can produce the result they need. Every claim must be verifiable; every number must be sourced from `stats.md`; every quote must be from a real, consented testimonial. No invention — refusal is the correct response when there's no eligible story. ## Inputs Required (asked at start if not given): - **Site** — must match a folder under `sites/[name]/`. - **Story ID** — references the entry in `sites/[site]/references/stories.md` (or `stories.{lang}.md` for multilingual). Format: `story-{slug}` matching the heading anchor in stories.md. Optional (per-run overrides): - **Industry / vertical** — used as the H1's qualifying detail and the schema `industry` field. Defaults to the story's industry. - **Anonymize** — `true` (default) | `false` (only if the story file marks the client as having given explicit consent for name use). If consent flag is missing, anonymize is forced true. ## Workflow This skill follows `/blog`'s workflow (Steps 0–11) with the page-type-specific differences listed below. Read `.claude/skills/blog/SKILL.md` end-to-end before running. ### What's unique to `/case-study` **Step 2 — Story selection (not keyword selection):** - Read `references/stories.md` (per-site, per-language). - The user supplies the story ID, or the skill picks the highest-impact unused story (one with the lar