agentleFS
45ck45ck/business-analysis-skills/.claude/skills/acceptance-criteria-writer/SKILL.md

acceptance-criteria-writer

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add failure, validation, permission, state, and edge-case behavior.

    line 32
  2. Very specific:

    Use Given/When/Then or equivalent observable format.

    line 33
  3. Distinctive:

    No hidden implementation detail unless intentionally required.

    line 39
  4. Distinctive:

    Prefer short, testable statements over long prose.

    line 48
  5. Distinctive:

    Do not invent stakeholder intent.

    line 53
  6. Distinctive:

    Do not convert preferences into mandatory requirements without evidence.

    line 54
  7. Distinctive:

    Do not hide unresolved ambiguity behind polished wording.

    line 55
  8. Distinctive:

    Do not collapse functional, non-functional, and business rule concerns into one blob.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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-writer

Purpose

Convert requirements or stories into observable, testable acceptance criteria.

Trigger this skill when

  • Requirements are too high-level to test.
  • Stories exist but there is no clear done condition.
  • You need criteria before implementation or QA work.

Expected inputs

  • requirements
  • story or feature description
  • constraints
  • business rules

Deliverables

  • acceptance criteria
  • negative criteria
  • ready-for-test checklist

Operating procedure

  1. Rewrite each feature into actor + trigger + expected outcome.
  2. Add failure, validation, permission, state, and edge-case behavior.
  3. Use Given/When/Then or equivalent observable format.
  4. Mark any criteria blocked by unresolved ambiguity.

Quality gates

  • Criteria are observable and verifiable.
  • Criteria cover success and important failure modes.
  • No hidden implementation detail unless intentionally required.

Handoff targets

  • edge-case-elicitor
  • requirements-traceability-starter
  • test-design packs later

Output style

  • Be explicit about uncertainty.
  • Prefer short, testable statements over long prose.
  • Surface risk and ambiguity instead of guessing.
  • Separate facts, assumptions, constraints, and open questions.

Failure modes to avoid

  • Do not invent stakeholder intent.
  • Do not convert preferences into mandatory requirements without evidence.
  • Do not hide unresolved ambiguity behind polished wording.
  • Do not collapse functional, non-functional, and business rule concerns into one blob.

Minimum output skeleton

## Summary
## Findings
## Structured outputs
## Assumptions
## Constraints
## Open questions
## Recommended next skill

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.