What problem does it solve? Teams often write vague backlog items that name UI widgets instead of user outcomes, lack testable acceptance criteria, or hide multiple stories inside one. This Skill turns user needs into development-ready stories with a stable output schema that imports cleanly into Jira and Azure DevOps. ## Core Features & Use Cases - Mike Cohn story format: Produces As a / I want to / so that stories with three line tests that catch generic personas, widget-naming, and restated motivations. - Gherkin acceptance criteria: Generates Given/When/Then scenarios covering happy path, error path, and at least one negative case, enforcing the one-When-one-Then split-signal rule. - Story mapping with release slices: Builds a backbone of activities, steps, and stories, then cuts horizontal release slices starting with a walking skeleton. - Use Case: Given a problem statement or spec for a banking dispute feature, generate US-1 through US-7 with acceptance criteria, detect a two-When story and split it, then assemble a story map whose first slice spans the whole user journey. ## Quick Start Ask the assistant to write user stories with Gherkin acceptance criteria from your problem statement or spec, optionally requesting a full story map with release slices.
