Product & planning21 categories
Acceptance criteria for this
A feature heading into development this week.
Write acceptance criteria for the feature below. Each one testable, each about observable behaviour rather than implementation. Include at least two failure cases and one thing that is deliberately out of scope. If the description is too vague to write criteria from, tell me what is missing instead of inventing it. Feature:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Specs and stories. Turning a vague request into something a team can build: specs, PRDs, stories and acceptance criteria.
Related prompts
Turn a vague request into a real specSomeone asked for "a dashboard" and nobody has defined what that means.Write user stories that are not disguised tasksBreaking a feature into stories a team can actually pick up independently.Write acceptance criteria that can be testedA story is ready to start and "it should work well" is currently the only criterion.Draft a PRD from my notesThe work is agreed in conversation and now needs a document people can disagree with.Story or task in disguise?A backlog item that reads like an implementation note.Who is this for?A feature defined by what it does, not who wants it.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free