THE WORKBENCH / WELL MADE IDEAS
Acceptance Criteria Builder
Turn a rough request into a brief someone can build, discuss and check. Keep the goal, constraints and examples together.
Read our Privacy policy for how tool inputs and visit data are handled, and our Terms of use for reuse permissions and resource limitations.
Write the agreement before the work. Describe the goal, then give each case a starting point, an action and an observable result. Every field except constraints is required.
These actions replace the current draft. There is no automatic saving.
01 / THE INTENT
A short brief
Name the change in plain language. 0/120 characters
What does completing this task let someone do? 0/600 characters
Use a role, not a person's private details. 0/160 characters
Record limits, environments, explicit exclusions or unresolved assumptions. 0/1500 characters
02 / THE EXAMPLES
Acceptance cases
Up to eight cases. This is a drafting boundary, not a suggested test-coverage target.
BEFORE YOU CALL IT READY
Questions for a human review
- Would two readers agree on the starting state, action and result?
- Is each limit supported by a real requirement or clearly marked as an assumption?
- What evidence would demonstrate the outcome after implementation?
- Consider a refused action or failure. Write what the person sees and what remains unchanged.
- Consider a boundary: an empty value, an exact limit, a repeated action or an interrupted step.
- Record important limits or exclusions, or explicitly state that none are known yet.
These prompts are simple checks, not a quality score. Given/When/Then labels help organize prose; the exports are not executable Gherkin or automated tests.
A stronger brief starts with a better question.
Read Write a brief that can be checked or use the blank acceptance worksheet.
Method reference: Cucumber’s explanation of Given, When and Then.