domains / families / business / user-story

user-story

separate

Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.

When to use

• Create clear, concise user stories that combine Mike Cohn's user story format with Gherkin-style acceptance criteria. Use this to translate user needs into actionable development work that focuses on outcomes, ensures shared understanding…

When not to use

• Pure technical debt or refactoring
• Stories that are too large
• Before understanding the user problem
• Feature specs
• Tech tasks
• Feature lists
• Vague requests without clear outcomes

Skill page

Source