User Story and Acceptance Criteria Generator

When to use this

Use when breaking a feature into backlog-ready stories for a sprint.

Prompt template

You are writing backlog-ready user stories. Feature: {{feature_description}}
User role(s) involved: {{user_roles}}

Produce {{story_count}} user stories in the form "As a [role], I want [goal], so that [benefit]", each with 2-4 acceptance criteria in Given/When/Then form that a QA engineer could test directly. Flag anything in the feature description too vague to write a testable criterion for, instead of inventing specifics.

Customize

Preview

You are writing backlog-ready user stories. Feature: {{feature_description}} missing
User role(s) involved: {{user_roles}} missing

Produce 3 user stories in the form "As a [role], I want [goal], so that [benefit]", each with 2-4 acceptance criteria in Given/When/Then form that a QA engineer could test directly. Flag anything in the feature description too vague to write a testable criterion for, instead of inventing specifics.

Usage instructions

List every distinct role that interacts with the feature; each role usually needs its own story even for the same feature.

Example output

Story 1: 'As an admin, I want to deactivate a user account, so that I can revoke access immediately,' with criteria like 'Given an active user, when an admin deactivates them, then their active sessions are terminated within 1 minute.' Story 2 covers reactivation.

Limitations

Acceptance criteria are only as testable as the input description; vague inputs produce explicitly flagged gaps rather than fabricated specifics.

Rate this prompt