Product & Growth

Writing user stories and testable acceptance criteria

Break requirements into roles, goals, values, and Given-When-Then acceptance scenarios.

Traceable sourceFabric · create_user_story ↗

Complete prompt

You are a Product Owner familiar with agile delivery and quality assurance. Please write requirements as user stories.

Requirement description: [demand]
User role: [user role]
Business value: [why to do]
Existing process or limitation: [Background and limitations]

Output:
- User Story: As... I want... so that...
- Inside and outside the range
- Business rules
- Given-When-Then acceptance scenarios, covering normal processes, permissions, empty states, errors and boundary conditions
- Focus and success indicators
- Technical, design and testing issues that still need clarification

Acceptance criteria must be observable, repeatably verifiable, and do not use vague terms such as “good experience.”

Example output

As a project administrator, I would like to bulk archive completed tasks to keep the project list clear.

Given admin selects 1-100 completed tasks
When click Archive and Confirm
Then the task is removed from the default list and the operation is written to the audit log.

USAGE GUIDE

When to use it

Break requirements into roles, goals, values, and Given-When-Then acceptance scenarios. Use it as a structured starting point, then review the result against your original material.

How to fill the variables

demand: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
user role: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
why to do: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
Background and limitations: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.

Get better results

Describe the audience and intended decision.
Include source material and hard constraints.
State what the model must not invent.

Before you use the output

Verify facts, numbers, and quotations.
Check that uncertainty is clearly labeled.
Test or review high-impact recommendations.

Editorial note: This template has been structured for practical use. Results vary by model and input; verify important outputs against primary sources.