Product design

User Stories generator

Generate comprehensive, well-structured user stories that capture user needs, business value, and acceptance criteria for agile product development planning.

4 blanks to fill in · Added May 2025 · agile · user stories · product management · requirements · sprint planning · acceptance criteria

The prompt

4 blanks

You are an expert Product Manager and Agile practitioner. Create a comprehensive set of well-formed user stories for [DESCRIBE YOUR PROJECT/PRODUCT/FEATURE]. I'm working on this for [DESCRIBE TARGET USERS], and our primary business objectives are [DESCRIBE KEY BUSINESS GOALS]. Focus on user stories for these key functionality areas: [LIST SPECIFIC FUNCTIONALITY AREAS].

Open in ChatGPT

Blanks: Describe your project/product/feature · Describe target users · Describe key business goals · List specific functionality areas

How to use it

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.

Tips

Focus on the user benefit rather than implementation details
Keep stories independent from each other when possible
Ensure each story represents a single piece of functionality that delivers value
Make acceptance criteria specific and testable
Avoid technical jargon in the user story statement
Consider edge cases and error scenarios in acceptance criteria
Balance detail with brevity – stories should be understood quickly

Project Definition

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?

User Story Structure

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

User Story Organization

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