User Story Creation

Breaking down epics into user stories involves identifying specific user journeys and scenarios within the larger epic, then creating individual stories with clear acceptance criteria. This Skill guides you through that process, ensuring each story follows INVEST principles—making them independent, negotiable, valuable, estimable, small, and testable—so your team has actionable requirements.

Acceptance criteria are specific, verifiable conditions that define when a user story is complete. They provide developers with concrete requirements and testers with measurable outcomes. This Skill helps you define clear acceptance criteria for each story, often in Given-When-Then format, eliminating ambiguity and reducing rework.

INVEST criteria—Independent, Negotiable, Valuable, Estimable, Small, and Testable—create stories that are realistic to estimate and execute. This Skill guides you through validating each criterion, helping you avoid stories that are too large, dependent on others, or unclear in value.

Effective user stories start with identifying user journeys from your epic, then crafting individual stories with clear acceptance criteria and definition of done. This Skill automates that workflow, generating story templates in standard formats so your development team receives well-formed requirements aligned with agile best practices.

Yes. This Skill is designed for agile workflows and integrates with standard story formats and templates used in project management tools like GitHub Projects, making it straightforward to export and track stories throughout your development cycle.

Stories that violate INVEST principles—such as being too large, tightly coupled, or vague—create estimation and execution challenges. This Skill identifies gaps against INVEST criteria and helps you refine stories into smaller, independent, testable units your team can confidently commit to.