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.

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, 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

For each goal, write at least one criterion describing an observable outcome.
Phrase criteria so they can be checked by a test, a command, or direct observation.
Avoid implementation detail; criteria describe behavior, not mechanism.
Cover edge cases and error behavior, not just the happy path.
Mark each criterion with how it will be verified.
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.