What problem does it solve? Customer case studies aimed at engineers usually collapse into testimonials: unverified numbers, paraphrased quotes, no limitations, and approval chains that stall or blow up after drafting. This Skill turns a real production deployment into a technical case study engineers trust, with every claim classified by evidence class, every number tied to an instrument and measurement window, and naming, quote, and security approvals cleared before publication. ## Core Features & Use Cases - Story qualification and ranking: Five gates (production not pilot, measured before-state, a named human, a reusable decision, a path to approval) decide whether a story is publishable, and an efficiency ranking picks which adopter to chase first when several candidates exist. - Evidence discipline: An evidence ledger classifies every claim as measured, partially measured, reported, or directional, and blocks annualized figures, unconfirmed derived percentages, and numbers the customer cannot vouch for. - Approval and anonymization workflow: A four-permission consent chain, pre-redaction of what security review predictably strikes, and a five-rung anonymization ladder for when naming is refused. - Use Case: You finished migrating a customer's billing pipeline onto your workflow engine and have a call recording plus a metrics screenshot. The Skill produces a verdict, an evidence ledger, an eight-section draft with verbatim quotes and a limitations section, an approval package with a dated deadline, and a seven-check gate report before anything ships. ## Quick Start Ask the assistant to write a technical case study from your customer interview transcript and metrics, and have it produce the verdict and evidence ledger before drafting.
