What problem does it solve? Writing implementation-ready user stories by hand often produces vague, incomplete tickets that cause developers to reinvent solutions, use wrong libraries, or miss critical requirements. This Skill generates a dedicated story file containing all the context a dev agent needs to implement the work correctly. ## Core Features & Use Cases - Story File Generation: Populates a structured template with summary, narrative description, testable acceptance criteria, solution approach, and impact analysis. - Complexity-Driven Structure: Adjusts story content based on story point estimates, adding sequenced TASK tables with dependencies for SP 8+ and split warnings for SP 21. - Quality Validation Checklist: Includes a review workflow that re-analyzes epics, architecture docs, and previous stories to catch missing requirements, wrong library choices, and regression risks before development starts. - Use Case: After analyzing a Jira ticket, ask the agent to create the next story; it produces a ready-for-dev story file with AC, technical guidance, and task breakdown saved to your project structure. ## Quick Start Ask the agent to create the next story for your current epic using the bmad-create-story workflow.
