agentleFS
Sign inStart free
roronoazoroshao369roronoazoroshao369/vibe-coding-os/skills/core/acceptance-criteria/SKILL.md

acceptance-criteria

Skill1 starsChanged 5 months agoMITView on GitHub

Write observable, testable acceptance criteria that connect intent to verification, so "done" is defined before work starts and checked objectively afterward. Use during specification, when refining a vague request, and during checkpoint validation to confirm a phase actually met its criteria. The spec intent, user scenarios, constraints, and any existing partial criteria. A list of acceptance criteria, each observable and paired with a verification method. - Applied: acceptance criteria as required, observable spec content from github/spec-kit. - Not applied: upstream…

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

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 6

    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:

    Write observable, testable acceptance criteria that connect intent to verification, so "done" is defined before work starts and checked …

    line 16
  2. Distinctive:

    Use during specification, when refining a vague request, and during checkpoint validation to confirm a phase actually met its criteria.

    line 21
  3. Distinctive:

    Avoid implementation detail.

    line 32
  4. Distinctive:

    Remove criteria that cannot be observed or that restate the implementation.

    line 35
  5. Distinctive:

    Only the happy path is covered.

    line 45
  6. Distinctive:

    Not applied: upstream phrasing or template text.

    line 58

“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

Acceptance Criteria

Purpose

Write observable, testable acceptance criteria that connect intent to verification, so "done" is defined before work starts and checked objectively afterward.

When to use

Use during specification, when refining a vague request, and during checkpoint validation to confirm a phase actually met its criteria.

Inputs

The spec intent, user scenarios, constraints, and any existing partial criteria.

Workflow

  1. For each goal, write at least one criterion describing an observable outcome.
  2. Phrase criteria so they can be checked by a test, a command, or direct observation.
  3. Avoid implementation detail; criteria describe behavior, not mechanism.
  4. Cover edge cases and error behavior, not just the happy path.
  5. Mark each criterion with how it will be verified.
  6. Remove criteria that cannot be observed or that restate the implementation.

Outputs

A list of acceptance criteria, each observable and paired with a verification method.

Failure modes

  • Criteria are subjective ("works well") and cannot be checked.
  • Criteria encode a specific implementation.
  • Only the happy path is covered.
  • Criteria exist but are never used as a gate.

Verification checklist

  • Each criterion is observable and testable.
  • Each criterion names a verification method.
  • Edge cases and errors are covered.
  • No criterion restates implementation detail.

Applied / Not Applied

  • Applied: acceptance criteria as required, observable spec content from github/spec-kit.
  • Not applied: upstream phrasing or template text. Criteria feed the local spec, checkpoint, and TDD skills.

Ghi chú tiếng Việt

Viết tiêu chí chấp nhận quan sát được, kiểm chứng được, nối ý định với verification. Tránh mô tả cách triển khai; bao phủ cả edge case và lỗi; mỗi tiêu chí nêu cách kiểm tra. Dùng làm cổng tại checkpoint. Liên kết: skills/core/spec-first-development/SKILL.md, skills/core/checkpoint-validation/SKILL.md.

Related quality packs

  • Acceptance Criteria Quality Pack (templates/quality-packs/acceptance-criteria-pack.md) — Structured quality levels (Basic, Verified, Gated, Audited) for AC rigor, with reusable criteria patterns, gate-pass criteria, and level selection guidance.
  • Workflow doc (docs/workflows/acceptance-criteria-quality-pack.md) — Step-by-step guide for selecting, applying, and interpreting the AC quality pack, integrated with checkpoints and scorecards.

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