What problem does it solve? Teams often start development without a shared, objective definition of done, leading to ambiguous requirements, scope creep, and disputes over whether a feature is finished. This Skill establishes clear, testable completion conditions before implementation begins. ## Core Features & Use Cases - Multiple Criteria Formats: Supports scenario-based (Given/When/Then), rule-based, and outcome-based acceptance criteria formats. - Structured Operating Procedure: Guides a five-step process covering intended outcomes, success conditions, failure conditions, completion boundaries, and testability validation. - Template-Driven Outputs: Produces standardized acceptance criteria documents with success conditions, failure conditions, business rules, boundary conditions, and traceability to requirements and user stories. - Use Case: When refining a user story like "users can log in", use this Skill to produce verifiable criteria covering valid credentials, invalid inputs, permission limits, and boundary conditions before developers write any code. ## Quick Start Ask the AI to define acceptance criteria for your user story or requirement, covering success conditions, failure scenarios, and completion boundaries.
