agentsclimarketplace
Sign in

Acceptance criteria

Skill roronoazoroshao369/vibe-coding-os/skills/core/acceptance-criteria

Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.From the repository description

Install
npx -y skills add roronoazoroshao369/vibe-coding-os --skill acceptance-criteria

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 573 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most product spec skills give in 573 tokens

Counted across 483 of the 502 authors here whose files we hold, read 2026-09-06

  • Write the PRD using the templatein 39 of 483, across 36 files
  • Ask one question at a timein 24 of 483
  • Write acceptance criteria in Given-When-Then formatin 24 of 483
  • Write user stories with acceptance criteriain 22 of 483, across 21 files
  • Respect ADRs in areas you touchin 21 of 483, across 17 files
  • Use the domain glossary vocabulary throughout the PRDin 20 of 483, across 16 files
  • Explore the repo to understand the current codebasein 19 of 483, across 15 files
  • Provide testable acceptance criteriain 19 of 483, across 17 files
  • Publish the PRD to the issue trackerin 18 of 483, across 14 files
  • Apply the ready-for-agent triage labelin 15 of 483, across 13 files
  • Prefer existing seams over new onesin 14 of 483, across 12 files
  • Save the PRD as a markdown filein 14 of 483, across 9 files

Said here and by no other author read

  • Phrase criteria so a test or command can check them
  • Mark each criterion with its verification method
  • Remove criteria that cannot be observed
  • Remove criteria that restate the implementation
  • Use criteria as a checkpoint gate

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.