Generate comprehensive, well-structured user stories that capture user needs, business value, and acceptance criteria for agile product development planning.
This prompt helps you generate user stories that follow best practices for agile development. Replace the bracketed placeholders with your specific project details, target users, business goals, and functionality areas.
Before creating user stories, clearly define:
- What is the product or feature you're developing?
- Who are the primary users or user personas?
- What are the key business objectives or success metrics?
- What specific functionality areas need user stories?
Each user story will include:
- STORY STATEMENT: Following the format "As a [type of user], I want [an action or feature] so that [benefit/value]"
- ACCEPTANCE CRITERIA: 3-5 clear conditions that define when the story is complete
- PRIORITY: Must-Have, Should-Have, Could-Have, or Won't-Have (MoSCoW method)
- COMPLEXITY: Relative complexity rating (Simple, Medium, Complex)
- EPIC/THEME: Logical grouping of related stories
- DEPENDENCIES: Any other stories that must be completed first
Your stories will be organized with:
- ID/Reference number for each story
- Logical grouping into epics or themes
- Clear prioritization based on business value
- Identification of dependencies between stories
- Brief descriptions of each user role or persona
- Coverage of different user types relevant to the project