acceptance-criteria
Skill2 starsChanged 5 days agoMITView on GitHub
Define measurable, testable success criteria before starting work, so completion is clear and verifiable. Use for features, documents, content, campaigns, or any non-trivial deliverable.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- jjdmev2/dme-skillstheir own version, first seen Nov 16, 2026
- roronoazoroshao369/vibe-coding-ostheir own version, first seen Nov 15, 2026
- celestialdust/achilles-skillstheir own version, first seen Nov 1, 2026
- MiguelSavignano/claude-code-systemtheir own version, first seen Nov 1, 2026
- Happy-Technologies-LLC/happy-platform-skillstheir own version, first seen Nov 1, 2026
- Tngc93/product-management-skillstheir own version, first seen Oct 20, 2026
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- Happy-Technologies-LLC/happy-platform-skills★ 41same name
- jdm4pku/RE-Skills★ 26same name
- MiguelSavignano/claude-code-system★ 7same name
- Sunnyshinnny776/pm-agentic-cookbook★ 4same name
- HamzaSheikh768/Agents-Skills-Lap★ 3same name
- jjdmev2/dme-skills★ 3same name
- designedbythanh/ai-skills-library-product-design★ 2same name
- garthcodes/claude-skills★ 2same name
- smarzban/agent-sdlc★ 2same name
- celestialdust/achilles-skills★ 1same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- decision-recordSkill
- hub-managerSkill
- memorySkill
- orchestratorSkill
- quality-gateSkill
- report-pdfSkill
- self-critiqueSkill
- source-verificationSkill
- structured-handoffSkill
- task-intakeSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Before implementing, writing, or producing anything non-trivial.
- Distinctive: line 15
When "done" is not obvious or needs to be aligned with the user.
- Distinctive: line 20
If criteria already exist and have not changed: reuse them.
- Distinctive: line 24
Start from the goal (from intake if available).
- Distinctive: line 25
Write 3 to 7 criteria, each observable: a behavior, a file, a metric, a format.
- Distinctive: line 27
Add essential edge cases (empty input, failure modes, different platforms).
- Distinctive: line 29
If a criterion depends on a user decision, ask now.
- Distinctive: line 43
Avoid vague criteria ("works well", "is clear"): transform them into something verifiable.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Acceptance Criteria
Defines what must be true for work to be considered complete, and how to verify it.
When to use
- Before implementing, writing, or producing anything non-trivial.
- When "done" is not obvious or needs to be aligned with the user.
When not to use
- Trivial fixes with an evident outcome (a typo, a name).
- If criteria already exist and have not changed: reuse them.
Procedure
- Start from the goal (from intake if available).
- Write 3 to 7 criteria, each observable: a behavior, a file, a metric, a format.
- For each criterion specify how it is verified: an automated test, a command, a manual check, a primary source.
- Add essential edge cases (empty input, failure modes, different platforms).
- Specify what is out of scope, preventing unrequested work.
- If a criterion depends on a user decision, ask now.
Expected output
Criteria:
1. <what must be true> — verification: <how>
…
Edge cases: …
Out of scope: …Attention
- Avoid vague criteria ("works well", "is clear"): transform them into something verifiable.
- Criteria are verified at the end using
quality-gate, never assumed to be satisfied.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

