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.