agentleFS
Sign inStart free
irwebtoolsirwebtools/Product-Skills/skills/product/acceptance-criteria/SKILL.md

acceptance-criteria

Skill0 starsChanged 2 months agoMITView on GitHub

Define testable acceptance criteria for Product validation.

16 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 7

    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
  1. Distinctive:

    Use when the task matches: acceptance-criteria, AC, definition of done.

    line 10
  2. Distinctive:

    Write criteria Product can demonstrate without reading code.

    line 24
  3. Distinctive:

    Keep Product validation and engineering verification distinct.

    line 38
  4. Distinctive:

    Do not claim completion without evidence.

    line 39
  5. Distinctive:

    Do not use vague criteria such as user-friendly.

    line 43
  6. Distinctive:

    Do not treat developer unit tests as Product acceptance.

    line 44
  7. Distinctive:

    Do not add hidden scope through criteria.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 12 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

acceptance-criteria

When to use

Use when the task matches: acceptance-criteria, AC, definition of done.

Purpose

Make success observable for Product review before developer handoff.

Inputs

  • User stories
  • Business rules
  • Scope boundary

Process

  1. Write criteria Product can demonstrate without reading code.
  2. Include happy path and important failure cases.
  3. Align criteria with validation and verification skills.
  4. Mark deferred criteria explicitly.

Outputs

  • Acceptance criteria per story
  • Negative cases
  • Demo checklist

Verification

  • Confirm each output exists and is reviewable.
  • Keep Product validation and engineering verification distinct.
  • Do not claim completion without evidence.

Restrictions

  • Do not use vague criteria such as user-friendly.
  • Do not treat developer unit tests as Product acceptance.
  • Do not add hidden scope through criteria.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free