user-story

This skill provides a standardized framework for product managers and technical teams to craft high-quality user stories that bridge the gap between user needs and actionable engineering tasks. By combining the Mike Cohn user story format—As a [persona], I want to [action], so that [outcome]—with Gherkin-style acceptance criteria, it ensures that every feature is grounded in user value while remaining technically verifiable.

• Employs the standard industry format: As a [persona], I want to [action], so that [outcome].

• Integrates Gherkin syntax (Given/When/Then) for precise, testable acceptance criteria.

• Promotes a conversational approach to product development, acting as a prompt for collaboration rather than a static technical specification.

• Incorporates validation checks to ensure stories are outcome-focused and avoid common anti-patterns like task-based requirements or feature bloat.

• Facilitates clarity between product, design, and engineering teams, reducing ambiguity during sprint planning and backlog grooming.

• Use this skill when you need to translate vague customer feedback or high-level goals into concrete, actionable development tickets.

• Perfect for sprint planning, backlog refinement, and preparing requirements for QA and development cycles.

• Avoid using this for pure technical debt or infrastructure refactoring tasks; for those, utilize dedicated engineering task frameworks.

• If a story grows too complex, use this alongside splitting strategies to break it into smaller, independently deliverable user stories.

• Ensure you have a defined persona and problem statement before initiating this skill to maintain user-centricity.

• The output is optimized for clarity, focusing on measurable outcomes and testable success conditions that help prevent scope creep and ensure shared understanding across the team.