<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -- Acceptance Criteria Acceptance criteria define the observable behavior that must be true for a story or feature to be considered done. This skill turns feature context into concise, testable Given/When/Then scenarios that engineers and QA can verify without guessing intent. When to Use - After a user story, PRD section, or feature slice is defined - When a team needs clear pass/fail conditions for implementation - When writing QA-ready criteria for sprint planning or handoff - When a story has edge cases, error p…