user-story

This skill provides a rigorous framework for product managers to transform abstract user needs into actionable development tasks. By bridging the gap between product discovery and engineering execution, it ensures that every piece of work is rooted in user value, maintains technical clarity, and remains verifiable through automated or manual testing.

• Employs the classic Mike Cohn User Story format: As a [persona], I want to [action], so that [outcome].

• Integrates Gherkin-style syntax for acceptance criteria (Scenario, Given, When, Then) to ensure testability and shared understanding.

• Focuses on outcome-based development rather than mere task tracking or feature lists.

• Provides built-in quality checks to prevent common anti-patterns like vague goals or excessively large user stories.

• Facilitates better collaboration between product, design, and engineering teams by establishing a common language for requirements.

• Recommended for backlog grooming, sprint planning, and documenting new feature requests.

• Works best when combined with preceding problem statements or proto-persona definitions for full context.

• Encourages splitting overly complex stories to maintain focus and velocity.

• Inputs typically include user persona, identified pain points, and desired outcomes.

• Outputs consist of a structured Markdown artifact ready for project management tools like Jira, GitHub Issues, or Linear.

• Not intended for low-level technical debt tasks or purely architectural refactoring, which should be managed as engineering tasks.