---
name: case-study
description: >
  Guided entry point for the Case Study & Capability Writer plugin. Routes to the correct
  skill based on what you need to produce: client-facing case study, award submission,
  partner evidence package, internal win story, or metrics collection. Runs the full pipeline
  or individual skills depending on the argument supplied.
---

# /case-study

Guided entry point for the Case Study & Capability Writer plugin.

## Usage

```
/case-study                                              # interactive guided mode
/case-study draft <brief-file>                           # draft a client-facing case study
/case-study award --body sitecore|optimizely|webby|other # write an award submission
/case-study evidence --partner microsoft|sitecore|optimizely  # assemble partner evidence package
/case-study win-story [<project-notes-file>]             # internal win story brief
/case-study metrics [<project-folder>]                   # collect and structure project metrics
/case-study review <draft-file>                          # run case-study-reviewer on a draft
```

## Routing logic

When invoked with no arguments or `guided`, ask:

```
What do you need to produce?

1. Client-facing case study (web + PDF one-pager)  → case-study-draft
2. Award submission                                 → award-submission-writer
3. Partner tier evidence package                   → partner-evidence-package
4. Internal win story (sales enablement)           → win-story-brief
5. Collect and structure project metrics first     → metrics-collector
6. Review a draft before it goes out               → case-study-reviewer (agent)
```

Route to the appropriate skill based on the user's response.

## Subcommand routing

| Subcommand | Routes to | Notes |
|---|---|---|
| `draft` | `case-study-draft` | Pass remaining args through |
| `award` | `award-submission-writer` | `--body` is required |
| `evidence` | `partner-evidence-package` | `--partner` is required |
| `win-story` | `win-story-brief` | Run immediately after project close |
| `metrics` | `metrics-collector` | Run before drafting when metrics are scattered |
| `review` | `case-study-reviewer` (agent) | Pass draft file path |

## Full pipeline (recommended for new projects)

For a new project with no existing case study material, the recommended pipeline is:

1. `/case-study metrics <project-folder>` — collect and structure metrics
2. `/case-study win-story` — capture the internal story while it is fresh
3. `/case-study draft` — produce the client-facing case study (uses metrics register)
4. `/case-study review <draft-file>` — independent review before sharing
5. `/case-study award --body <body>` — nomination when an award window opens
6. `/case-study evidence --partner <partner>` — renewal evidence when tier renewal approaches

## Examples

```
/case-study draft briefs/acme-replatform.md --platform sitecore --format both
/case-study award --body sitecore --category "Best Migration"
/case-study evidence --partner microsoft --tier specialisation --renewal-date 2026-09-01
/case-study win-story retros/globex-project-retro.md --sector financial-services
/case-study metrics projects/acme/ --source lighthouse --go-live-date 2026-03
/case-study review output/acme-case-study-draft.md
```