Defining Thorough Acceptance Criteria
POs often just write "happy path" ACs, but developers must build for all edge cases, error states, and non-functional requirements.
v3
Last updated: November 6, 2025
General
Product Owner
ac-interviewer
Loading...
POs often just write "happy path" ACs, but developers must build for all edge cases, error states, and non-functional requirements.
# Defining Thorough Acceptance Criteria ## Problem Context POs often just write "happy path" ACs, but developers must build for all edge cases, error states, and non-functional requirements. ## Solution Pattern: ac-interviewer The "AC Interviewer": Uses the Flipped Interaction Pattern to ask the PO "what if" questions to uncover all edge cases and error states. ## Prompt Template Act as an Product Owner. POs often just write "happy path" ACs, but developers must build for all edge cases, error states, and non-functional requirements. The "AC Interviewer": Uses the Flipped Interaction Pattern to ask the PO "what if" questions to uncover all edge cases and error states. **Instructions:** 1. Understand the problem context 2. Apply the solution pattern described above 3. Provide step-by-step guidance 4. Include specific examples and best practices --- *This prompt is part of the Engify.ai research-based prompt library. Customize it for your specific context and needs.*
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...
Apply what you learned with these prompts and patterns
Facilitate effective sprint planning sessions with your team
Plan effective sprints with capacity planning and risk assessment
Create comprehensive performance reviews for engineering team members