agentleFS
Tngc93Tngc93/product-management-skills/skills/acceptance-criteria/SKILL.md

acceptance-criteria

Skill0 starsChanged 34 days agoMITView on GitHub

Write acceptance criteria and test scenarios for a user story or requirement in Given/When/Then (Gherkin), including edge cases, error paths and non-functional checks, so that a developer and a tester agree on "done" before work starts. Use when the user asks for acceptance criteria, test cases, test scenarios, Gherkin, BDD, definition of done, or QA handoff for a story.

18 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

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start from pm-skills template acceptance-criteria.

    line 29
  2. Very specific:

    Use concrete example data (a cart of 3 items totalling 1,250 TL), not placeholders.

    line 33
  3. Distinctive:

    Use the domain's words, not UI implementation details, unless the detail is the requirement.

    line 34
  4. Very specific:

    If the team writes in Turkish, Turkish Gherkin keywords are fine: Senaryo, Diyelim ki, Eğer ki, O zaman, Ve.

    line 35
  5. Very specific:

    Run pm-skills lint <file> --type criteria.

    line 39

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

Write acceptance criteria

Acceptance criteria are the contract for "done". Each one must be checkable by someone who did not write it, without asking the author what they meant.

CLI: node "${CLAUDE_PLUGIN_ROOT}/cli/pm-skills.mjs" (or ../../cli/pm-skills.mjs relative to this file). Below, pm-skills.

1. Understand the story

Read the story and its parent PRD if there is one. Identify the actor, the trigger, the expected outcome and the business rules involved. If a rule is ambiguous (what happens at exactly the limit? who sees what?), list it as a question rather than picking an answer silently.

2. Find the scenarios

Work through these, in order, and keep the ones that apply:

  1. Happy path: the main thing working.
  2. Business rules: one scenario per rule, including the exact boundary (at 100, at 101).
  3. Alternative paths: other valid ways to get the outcome.
  4. Errors and empty states: invalid input, missing data, no results, timeouts, the other system being down.
  5. Permissions: who must not be able to do this.
  6. Non-functional, only where they matter for this story: performance budget, accessibility, localisation, analytics events, audit trail.

3. Write them

Start from pm-skills template acceptance-criteria. Rules:

  • One behaviour per scenario. One When per scenario.
  • Given sets up state, not actions. Then describes something observable: what the user sees, what is stored, which event is sent. Never "the system works correctly".
  • Use concrete example data (a cart of 3 items totalling 1,250 TL), not placeholders. Use a Scenario Outline with an Examples table when only the data changes.
  • Use the domain's words, not UI implementation details, unless the detail is the requirement.
  • If the team writes in Turkish, Turkish Gherkin keywords are fine: Senaryo, Diyelim ki, Eğer ki, O zaman, Ve.

4. Check

Run pm-skills lint <file> --type criteria. Every scenario must have Given, When and Then; criteria using "should" without anything measurable are flagged; vague words are flagged.

Return the scenarios plus a short list of the questions you could not resolve, each with who should answer it.

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.