Product
Share

Acceptance Criteria Generator

Generate comprehensive, testable acceptance criteria for user stories and features.

Use Case

Creating acceptance criteria for user stories, defining testable requirements, or ensuring feature completeness.

Prompt

Generate acceptance criteria for [user story/feature].

Context:
- User story/feature: [describe]
- User goal: [describe]
- Technical context: [describe]

Provide:

1. Acceptance Criteria Overview
   - Feature description
   - User story (if applicable)
   - Definition of done

2. Happy Path Criteria
   - Primary user flow
   - Step-by-step success criteria
   - Expected outcomes
   - Success indicators

3. Edge Cases
   - Boundary conditions
   - Unusual inputs
   - Extreme scenarios
   - Special cases

4. Error Handling
   - Error scenarios
   - Error messages
   - Recovery paths
   - User feedback

5. Validation Rules
   - Input validation
   - Business rule validation
   - Data validation
   - Permission validation

6. State Management
   - Initial state
   - State transitions
   - Final state
   - State persistence

7. UI/UX Requirements
   - Visual requirements
   - Interaction requirements
   - Responsive requirements
   - Accessibility requirements

8. Performance Criteria
   - Load time requirements
   - Response time requirements
   - Throughput requirements
   - Resource usage limits

9. Integration Criteria
   - API integration
   - Third-party services
   - Data synchronization
   - External dependencies

10. Testing Requirements
    - Unit test requirements
    - Integration test requirements
    - E2E test requirements
    - Manual test scenarios

Format as specific, testable acceptance criteria ready for development and QA.

How to use

  1. 1Replace [user story/feature] and [describe] placeholders with your specific details
  2. 2Describe the user story/feature: Replace [User story/feature] with your feature (e.g., "User profile update" or "Checkout flow")
  3. 3Describe user goal: Replace [User goal] with what users want to achieve (e.g., "Update profile information quickly")
  4. 4Describe technical context: Replace [Technical context] with technical details (e.g., "React component, REST API, PostgreSQL database")
  5. 5If you have user story: Paste your user story. Say "User story: [paste story]"
  6. 6If you have requirements: Paste feature requirements. Say "Feature requirements: [paste requirements]"
  7. 7Paste the modified prompt into your preferred AI tool, like ChatGPT or Claude
  8. 8Review the acceptance criteria: Check happy path, edge cases, error handling, and validation rules
  9. 9Verify testability: Ensure all acceptance criteria are specific and testable
  10. 10Ask for refinements: Request "Add more edge cases" or "Expand error handling" or "Detail validation rules"
  11. 11Export to your tool: Copy the acceptance criteria to Jira, Linear, or your product management tool

Pro Tips

  • Specify user story format: Mention "Agile user story format" or "Given-When-Then format" if you prefer a specific format
  • Include technical context: Mention your tech stack (e.g., "React, TypeScript, REST API") so AI includes relevant technical criteria
  • Request prioritization: Ask "Prioritize acceptance criteria (P0/P1/P2)" for critical vs nice-to-have criteria
  • For complex features: Break down complex features into smaller acceptance criteria sets
  • Save as template: Reuse the acceptance criteria structure for future user stories

Tags

acceptance-criteriarequirementstestingspecificationagile

New prompts & templates by email

Weekly copy-paste prompts, pattern notes, and AI UX resources on Substack - no spam, unsubscribe anytime.

Subscribe on Substack