What problem does it solve? Technical artefacts like PRDs, stories, and features describe implementation details that founders cannot act on. This Skill converts that technical content into a single plain-English outcome line stating what the founder can now do, keeping founder-facing surfaces free of internal IDs, command names, and jargon. ## Core Features & Use Cases - Outcome Voice Rules: Enforces a one-sentence, second-person or capability-framed style with hard bans on internal IDs, command names, shell syntax, and jargon. - Strict Output Contract: Produces exactly one plain-text line under ~20 words (max 120 characters), with no markdown, labels, or quotes, persisted verbatim to the artefact's outcome field. - Honest Empty Handling: Returns an empty line when the artefact has no shipped capability, so producers leave the outcome blank rather than fabricating value. - Use Case: After drafting a story about dashboard auto-generation, a producer skill applies this rulebook inline to write: "You can now auto-generate dashboards from your requirements — ship faster without wiring widgets by hand." ## Quick Start Ask the producer skill drafting your PRD, feature, or story to apply the write-outcomes rules and add a one-line founder-facing outcome to the artefact.
