Agile User Story and Acceptance Criteria Writer

Complete user stories with Given/When/Then acceptance criteria, story points, and edge case coverage, ready for sprint planning.

Best For

•Product managers prepping for sprint planning who need dev-ready stories without a follow-up clarification meeting.
•Engineering leads breaking down a large feature request into estimable, independently shippable pieces.
•Scrum teams standardizing on Given/When/Then acceptance criteria who want consistent story formatting across the backlog.

Prompt Template

I need you to write agile user stories for the following feature: [FEATURE DESCRIPTION]. Our tech stack is [STACK, e.g., React frontend, Node.js API, PostgreSQL]. Our users are [USER TYPES, e.g., admin users and end customers]. For each user story: (1) write the story in the format "As a [role], I want to [capability] so that [benefit]", (2) write 3–5 acceptance criteria in Given/When/Then format, (3) flag any technical dependencies, API calls, or database changes required, (4) estimate a story point value (1, 2, 3, 5, or 8) with a one-line justification. Generate stories for these scenarios: happy path (the main use case working as expected), error states (what happens when the feature fails or receives bad input), and edge cases (boundary conditions, empty states, concurrent users). Format the output as a numbered list of stories, each complete enough for a developer to start implementation without needing a follow-up meeting.

Pro Tip

Name the actual user roles from your product, like 'warehouse manager' instead of 'user,' since generic roles produce acceptance criteria too vague for a developer to build against.

Example Output

A sample of what this prompt produces once you fill in the placeholders.

For a 'bulk CSV import' feature, the output produces a happy-path story ('As an admin, I want to upload a CSV of contacts so that I can add many records at once') with Given/When/Then criteria for a valid file, an error-state story for malformed CSVs, an edge-case story for a file exceeding the row limit, each with a story point estimate and a one-line justification.