Prompt details

Tested on

Claude Opus 5.5

Length

494 words · 3 fill-ins

Example input

[Feature description or PRD]: Self-service password reset for Larkfield Bank's mobile and web banking. Today a customer who forgets their password has to call support (about 3,100 calls a month). New flow: from the login screen, the customer taps "Forgot password", enters their username or email, and chooses to get a one-time code by email or by text message to the phone number on file. They enter the code, set a new password, and go back to the login screen to sign in with it. If they can no longer reach that email or phone, the screen tells them to call support. After a successful reset, the customer gets a notice on both email and text.

[User roles]: Retail customer: has personal accounts. Business user: one of several users on a business account; a business admin manages these users. Support agent: can see reset attempts in the support console; cannot see codes or set passwords. Fraud analyst: reviews resets flagged by the fraud rules.

[System constraints and rules]: Platforms: iOS app, Android app, web. Sign-in uses username, password and a registered device; signing in from a new device needs an extra check (already built). Codes: 6 digits, valid for 10 minutes, single use. After 5 wrong codes, reset is locked for 30 minutes. Password rules: at least 12 characters, not one of the last 5 passwords. Text messages go through our SMS vendor. Fraud rule: no codes by text to a phone number changed in the last 7 days. Every reset attempt is written to the audit log (who, when, channel, outcome). After a successful reset, all other sessions end. Error messages must not reveal whether a username or email exists. For business users, the business admin is notified when one of their users resets a password.

Example output

1. Story map

Epic 1: Email-code reset on web (walking skeleton: simplest end-to-end path)

- PR-01 Reset my password on web with an emailed code, starting from my username

- PR-02 Start a reset with my email address instead of my username

- PR-03 Stop me reusing one of my last 5 passwords

- PR-04 Lock reset after 5 wrong codes

- PR-05 End my other sessions after a reset

Epic 2: Text-message channel and change notice

- PR-06 Get my reset code by text message

- PR-07 Withhold text codes from a phone number changed in the last 7 days

- PR-08 Tell me by email and text that my password was reset

Epic 3: When self-service can't finish

- PR-09 Tell me to call support when I can't reach my email or phone

- PR-10 Support agent sees a customer's reset attempts

- PR-11 Fraud analyst reviews flagged resets

Epic 4: Mobile apps

- PR-12 Reset my password in the iOS app

- PR-13 Reset my password in the Android app

Epic 5: Business users

- PR-14 Business user resets their own password

- PR-15 Business admin is told when one of their users resets

> Release note: PR-01 to PR-10 together form the smallest set you can release to customers on web. Build earlier stories behind a release toggle. Whether PR-11 must ship at launch is a refinement question (see section 5).

---

2. Stories

PR-01 · Reset my password on web with an emailed code, starting from my username

As a retail customer, I want to reset my forgotten password on the web with a code sent to my email, so that I can get back into online banking without calling support.

Claude Opus 5.5

User Stories – User stories prompt for ChatGPT and Claude

^$9.99

Kept in your account
Copy filled in or download
Updates included

Pay once and keep it. Or get every premium prompt and skill with the plan, $19.99 a month. Payments are non-refundable. See our Terms.

votes views

Claude Opus 5.5

This prompt breaks a feature or PRD into backlog-ready user stories. Paste the feature, the user roles and the system rules; you get thin story slices, Given-When-Then criteria, edge cases, an INVEST check and refinement questions.

What you get

A story map: epics in delivery order, split into thin stories that each work end to end
Every story as "As a, I want, so that" with 3 to 6 Given-When-Then scenarios, negative paths included
The edge cases still uncovered, and an INVEST check with a fix for each story
Refinement questions grouped by who answers, each tagged with the stories it blocks

How to use it

1
Paste the feature and its rules
Give the flow step by step, every role, and every limit, timeout and security rule you know. Exact values become exact criteria.
2
Read the story map first
Check the order and the slices before the scenarios: the first story should work end to end on its own.
3
Take the questions to refinement
Settle each [confirm] with its owner, paste the answers back and ask for the stories updated before the team estimates.

Better results

Put every exact value you know (limits, timeouts, lengths) in the constraints. Each one you leave out comes back as [confirm], which is right but slows refinement.
Follow up with "Give me these stories as CSV with Summary, Description and Acceptance criteria columns" to import them into your backlog tool.
Send the refinement questions to the people named before the session, so the team estimates against answers rather than guesses.

Questions

Can ChatGPT write user stories?

Yes, ChatGPT can write user stories with acceptance criteria when you give it the feature, the roles and the rules. It is strongest on structure and negative paths. It cannot know your limits or message wording, so expect placeholders for the team to settle in refinement.

What is a good Copilot prompt for writing user stories?

A good Copilot prompt for user stories gives the feature, the user roles and the system rules, asks for thin slices with Given-When-Then criteria, and tells it never to invent limits. This prompt runs as it is in Microsoft Copilot.

How do business analysts use AI?

Business analysts use AI to draft user stories and acceptance criteria, find edge cases and negative paths, check stories against INVEST and list questions for stakeholders. It speeds up the first draft; the analyst still owns the decisions and the talks with the team.

What is the Given-When-Then format?

Given-When-Then is a way to write acceptance criteria as scenarios: Given the starting state, When the user acts, Then the result anyone can observe. Each scenario is one test, so testers can run it as written and tools such as Cucumber can automate it.

Updated 8 Nov 2026