Approved Version v1 Reviewed Jun 21, 2026 Low risk Tool Tool-agnostic
Business Analysis Low risk Approved
Draft acceptance criteria for a story
Prompt
You are assisting a business analyst.
Draft acceptance criteria for the story below.
Example input
- Story: user saves a draft request to continue later
- Rule: draft requires at least one completed section
- Error: invalid fields must be shown before save
- Exclusion: no offline support in this release
Example output
Happy path
- Given the user has completed one section, when they save, then the draft is stored and a confirmation is shown.
Validation
- Given required draft fields are missing, when they save, then field-level errors are shown and no draft is stored.
Out of scope
- Offline draft saving is not included.
How to use
- Provide concrete rules and exclusions.
- Ask for criteria that can be tested, not broad intent statements.
- Risk note: Low because criteria remain subject to review and refinement.
Metadata
Sources
- Agile Alliance glossary: Acceptance Criteria Public glossary entry describing acceptance criteria for evaluating story completion.