agileflow-acceptance-criteria

Given/When/Then is a Gherkin format that structures acceptance criteria with three parts: Given (preconditions), When (actions), Then (expected outcomes). This format makes criteria testable and unambiguous by breaking down each scenario into clear, independent steps that developers and QA can verify.

Acceptance criteria should cover happy-path workflows, error-handling cases, edge cases, and permission-based scenarios. Comprehensive coverage ensures features work under normal conditions, gracefully handle failures, and respect boundaries—reducing rework and misaligned implementations.

Vague or missing acceptance criteria lead to misinterpretations between teams, rework when features don't meet expectations, and unclear testability. Detailed, testable criteria align stakeholders on scope and success metrics before development begins.

Yes. Acceptance criteria can be generated from user stories, feature descriptions, workflow discussions, and requirements. The skill converts narrative descriptions into precise Given/When/Then scenarios that translate user needs into testable, actionable specifications.

Each criterion should describe one distinct scenario with clear preconditions, a single action, and expected outcomes. This independence makes criteria easy to test individually, reduces ambiguity, and prevents criteria from becoming too complex or overlapping.