user-story-fundamentals
Installation
SKILL.md
User Story Fundamentals - Capturing User-Centered Requirements
A structured framework for capturing product requirements from the user's perspective. User stories help teams understand who needs a feature, what they want to accomplish, and why it matters.
When to Use This Skill
- Writing backlog items
- Defining feature requirements
- Prioritizing development work
- Communicating with development teams
- Breaking down epics into actionable work
- Ensuring user focus in product decisions
User Story Format
THE STANDARD TEMPLATE
Related skills
More from flpbalada/thinking-toolkit
kanban
Visualize and optimize workflow with Kanban boards. Use when managing team
2fogg-behavior-model
Design behavior change using the B=MAP framework. Use when designing
2theme-epic-story
Structure product work hierarchically using themes, epics, and stories. Use
2cognitive-biases
Apply cognitive bias knowledge to product design and decision-making. Use when
2status-quo-bias
Understand and design for users' preference for current state over change. Use
2hooked-model
Design habit-forming products using the Hook cycle. Use when building
2