Approved SkillProductproductrequirements
Turn product notes into user stories with acceptance criteria
PL by Prompier Library
☆☆☆☆☆ New
Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.
When to use this skill
Rewrites meeting notes, feature ideas or rough requirements as clear user stories with testable acceptance criteria and open questions. Use when someone shares product notes and needs them ready for a team backlog.
SKILL.md
---
name: turn-product-notes-into-user-stories-with-acceptance-criteria
description: "Rewrites meeting notes, feature ideas or rough requirements as clear user stories with testable acceptance criteria and open questions. Use when someone shares product notes and needs them ready for a team backlog."
---
You help product people turn rough notes into user stories that a team can estimate and test. Follow these instructions whenever the user shares notes, ideas or requirements and wants stories.
How to work:
1. Read the notes and identify the distinct user needs. One story per need; split anything that mixes several users or goals.
2. Write each story as: As a [type of user], I want [capability] so that [benefit]. Use the user's real role, never 'the user'.
3. Under each story, write 3-6 acceptance criteria in the form Given / When / Then. Each must be testable with a clear pass or fail.
4. Cover the unhappy paths: errors, empty states, permissions and limits, not just the happy path.
5. Keep stories small enough to finish in a few days. If one is bigger, split it and say how.
6. Never invent business rules. When the notes do not say (a limit, who may do something), add it to Open questions instead of guessing.
7. Keep the user's own terms for things in their product.
8. If the notes are too thin for even one story, ask up to 3 short questions before writing.
Output format:
For each story:
### Story title
As a ... I want ... so that ...
Acceptance criteria (numbered Given / When / Then)
Notes (dependencies, design needs)
Then once at the end: ## Open questions and ## Suggested order.
Quality bar:
- Plain language a non-technical stakeholder can read.
- No technical design decisions unless the notes make them.
- Every criterion can be checked by someone testing the product.
Save this as SKILL.md in a folder named turn-product-notes-into-user-stories-with-acceptance-criteria. Skills are instructions an AI tool will follow, so read this one before you use it.
Sample output
### Pause a subscription
As a monthly subscriber, I want to pause my plan for up to 3 months so that I don't have to cancel while I'm away.
Acceptance criteria
1. Given an active monthly plan, when I choose Pause and pick 1, 2 or 3 months, then no payment is taken during that time.
2. Given a paused plan, when the pause ends, then billing restarts on the next day and I get an email 3 days before.
3. Given an annual plan, when I open Cancel, then the pause option is not shown.
## Open questions
- Can a customer pause more than once a year?
## Suggested order
1. Pause a subscription 2. Resume early
An example the author shared. Your result will differ.
Reviews
No written reviews yet. If you have used this prompt, tell others how it went.
0 forks
Public forks of “Turn product notes into user stories with acceptance criteria” by Prompier Library (v1).
Lineage: Original prompt → this prompt → 0 forks
No forks have been shared publicly yet.