acceptance-criteria-writer SKILL.md skillA
acceptance-criteria-writer from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/acceptance-criteria-writer@git:20260323.771ca1cPins git:20260323.771ca1c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/business-analyst/acceptance-criteria-writer/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260323.771ca1c, committed Mar 23, 2026
- Size
- 5,196 bytes
- Repository stars
- 21
- License
- MIT
Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".
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
## Overview Based on **Mastering the Requirements Process** by Suzanne & James Robertson - the Fit Criteria concept, where every requirement gets a quantified, measurable condition that proves it has been satisfied. Also draws on **User Stories Applied** by Mike Cohn for the 3 C's (Card, Conversation, Confirmation) where Confirmation = acceptance criteria, and **Writing Effective Use Cases** by Alistair Cockburn where the Success Guarantee (postcondition) is the use case's acceptance criterion. The key insight from Robertson: if you cannot write a fit criterion for a requirement, the requirement is too vague to implement. ## Workflow ### Step 1: Identify the requirement or story to test Start from a documented requirement (FR-XXX), user story, or use case. Extract: - **What** the system should do (the behavior) - **Why** it matters (the rationale - drives which edge cases to cover) - **Who** is the actor (drives the perspective of the criteria) ### Step 2: Write the primary acceptance criterion (happy path) Use Robertson's Fit Criterion format for precision: ``` FIT CRITERION: [Measurable condition that proves the requirement is met] …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/acceptance-criteria-writer@sha256:0af3002e15e2ac30The line at the top of this page pins the label git:20260323.771ca1c, 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_p3xd2gy4ok2wdvdw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 23, 2026.
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 (5196 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
qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p3xd2gy4ok2wdvdw GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/acceptance-criteria-writer GET https://markdownregistry.com/api/v1/blob/0af3002e15e2ac3024704de4681bd5b024d5a4212b72e532b635fc59d1051aff
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.
More from qa-aman/claude-skills
Every file in qa-aman/claude-skills