Acceptance Criteria
Acceptance Criteria Skill
Purpose
Define clear, testable acceptance criteria that specify exactly when a requirement or user story is considered complete and working correctly.
When to Use
- Writing user stories for Agile sprints
- Defining requirements in FRS
- Planning UAT test cases
- Creating Definition of Done for features
Acceptance Criteria Formats
1. Given-When-Then (Gherkin)
Structure:
Given [precondition/context]
When [action/event]
More from danhvb/my-ba-skills
erp domain knowledge
Understand ERP systems covering Finance, HR, Supply Chain, Manufacturing, and Procurement modules for enterprise implementations
105e-commerce domain knowledge
Understand e-commerce business models, core modules, and requirements patterns for B2C, B2B, C2C, and Marketplace platforms
90crm domain knowledge
Understand CRM systems covering Sales, Marketing, and Customer Service modules for lead management, pipeline tracking, and customer engagement
39process mapping
Create clear business process diagrams using BPMN, flowcharts, and swimlane diagrams for Web, Mobile, ERP, CRM, CDP, and E-commerce projects
34requirements elicitation
Guide AI assistants in conducting effective requirements gathering sessions using proven techniques for Web, Mobile, ERP, CRM, CDP, and E-commerce projects
34brd creation
Guide AI assistants in creating professional Business Requirement Documents for Web, Mobile, ERP, CRM, CDP, and E-commerce projects
33