The Case Study

Every shipped project should produce four or five downstream artifacts — a LinkedIn post, a GitHub README, resume bullets, a cover-letter paragraph, a portfolio writeup. In practice, each gets written separately, days apart, with drifting framing and inconsistent stats. The story you tell on LinkedIn is rarely the story you tell on your resume.

The Case Study skill takes a structured project brief and emits all four artifact formats in a single pass. The skill enforces a shared spine — problem, approach, what shipped, results, honest limits — and then re-renders that spine into each format's voice and length budget. The result is artifact set, not artifact list.

• One pass, four coordinated artifacts — no drift across surfaces
• Shared spine forces honest limits to appear everywhere, not just on the long version
• Markdown-first output drops cleanly into GitHub, LinkedIn, and resume editors
• Frees the writing time for the next project instead of repackaging the last one

Length budgets are the hard part — LinkedIn rewards specifics, resume bullets punish them. Next iteration: per-format tone presets and an artifact-level diff against the previous case study to catch unintentional voice changes.