Deliver Acceptance Criteria

Turns product specs into testable Given/When/Then acceptance criteria organized by happy path, edge cases, error states, and non-functional requirements. You'd reach for this during sprint planning or handoff when a story needs clear pass/fail conditions that engineering and QA can verify without interpretation. The structure forces you to separate primary flows from exceptions and make recovery behavior explicit, which catches the "what happens when the API is down" questions before they become blocking Slack threads. Includes a quality checklist that pushes back on subjective statements and implementation details leaking into criteria.

skills.sh installs: 1.1K
GitHub stars: 794
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria --agent claude-code

Installs into .claude/skills of the current project.

Files

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 paths, or non-functional expectations that should be explicit