business-story-narration

What problem does it solve?

Teams and AI assistants often conflate implementation details with user-facing intent, producing issue tracker entries that are either over-specified or ambiguous. This Skill separates the business-facing narrative from the engineer-facing contract so stakeholders and implementers share a clear, testable understanding of scope and success.

Core Features & Use Cases

• Business description generation: Produces a 1-3 sentence, non-technical summary that describes the user's experience and outcome.
• Acceptance criteria authoring: Generates measurable, independently verifiable criteria written as Given/When/Then or a checklist, covering happy and error paths.
• Technical notes (optional): Captures implementation-relevant details separately so the business layer remains free of component names, API paths, or framework references.
• Use case: Convert a set of architecture notes and a Figma screen into a product-ready story for Jira or Linear that product owners can approve and engineers can implement.

Quick Start

Using the /business-story-narration skill, produce a user story statement, a 1-3 sentence business description, and acceptance criteria for [story title] based on the provided story documents and designs.