deliver-acceptance-criteria SKILL.md skillA
deliver-acceptance-criteria from product-on-purpose/pm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add product-on-purpose/pm-skills/deliver-acceptance-criteria@v1.1.1Pins v1.1.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- product-on-purpose/pm-skills
- Path
skills/deliver-acceptance-criteria/SKILL.md- Versions recorded
- 8
- Latest version
- v1.1.1, committed Oct 30, 2026
- First version recorded
- Mar 23, 2026
- Size
- 4,316 bytes
- Repository stars
- 790
- License
- Apache-2.0
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- 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 paths, or non-functional expectations that should be explicit ## When NOT to Use - You need the user stories themselves -> use `deliver-user-stories`; this skill deepens a story that already exists - You need systematic failure coverage across a whole feature -> use `deliver-edge-cases`; this skill stays story-scoped - There is no story or slice to bind criteria to yet -> use `deliver-prd` or `deliver-user-stories` first - You are defining success metrics for an experiment, not done-ness for a story -> use `measure-experiment-design` …
Read the whole file at its exact version.
How to install
mdr add product-on-purpose/pm-skills/deliver-acceptance-criteria@sha256:60785011f3aea766The line at the top of this page pins the label v1.1.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ge2qqywdinnvjqbl)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Mar 23, 2026 and Oct 30, 2026, about one every 32 days. Its first recorded version is graded C and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.1 latest | 2026-10-30 | 1dfc0c8 | 4,316 B | A | view · diff |
| v1.1.1 | 2026-10-17 | 31e4692 | 4,316 B | A | view · diff |
| v1.1.1 | 2026-10-16 | 3b5d0d8 | 4,312 B | A | view · diff |
| v1.1.0 | 2026-06-10 | bf23914 | 4,060 B | A | view · diff |
| v1.0.1 | 2026-06-10 | b8ccff6 | 3,580 B | A | view · diff |
| v1.0.0 | 2026-05-20 | be1352b | 3,386 B | A | view · diff |
| v1.0.0 | 2026-03-25 | 0ab0a60 | 3,380 B | A | view · diff |
| git:20260323.8d2a418 | 2026-03-23 | 8d2a418 | 3,380 B | C | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4316 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
product-on-purpose/pm-skills · 790 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ge2qqywdinnvjqbl GET https://markdownregistry.com/api/v1/resolve?ref=product-on-purpose/pm-skills/deliver-acceptance-criteria GET https://markdownregistry.com/api/v1/blob/60785011f3aea766058f11b8afc345e24ebf99d340913069147483382d6be4f4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.