success-criteria

Generates machine-readable success criteria in qa-checklist.yaml from plans and specs.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/joydai2026-del/skills --skill success-criteria-joydai2026-del
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: success-criteria
Source: https://github.com/joydai2026-del/skills/tree/main/success-criteria
Command: npx skills add https://github.com/joydai2026-del/skills --skill success-criteria-joydai2026-del

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Vague or subjective success criteria cause QA loops that never close. This Skill converts any plan, spec, or task list into a structured YAML checklist where every requirement is either automatically testable (run a command, check output) or code-auditable (read specific files, verify logic), giving QA agents a precise target. ## Core Features & Use Cases - Requirement Classification: Splits plan requirements into automated checks (curl, build commands, test suites) and code-audit checks (UI logic, event handlers, business rules), maximizing automated coverage. - Structured YAML Output: Writes docs/qa-checklist.yaml with explicit comparison modes (exact, regex, numeric, exit_code), side-effect flags, stable category-based IDs, and status tracking for the QA checklist loop. - Incremental Updates: Auto-triggers on scope changes, bug reports, or feature feedback, updating only affected checks while preserving existing IDs and archiving removed ones. - Use Case: After writing a feature plan for a new checkout flow, run the Skill to produce a checklist covering every endpoint, UI state, and build gate, then hand it to the QA loop which iterates until all checks pass. ## Quick Start Ask the agent to generate success criteria from your plan file, for example: run /success-criteria docs/checkout-plan.md to produce docs/qa-checklist.yaml.

Frequently Asked Questions about success-criteria

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate acceptance criteria from a feature plan?▼

Run /success-criteria with the path to your plan file, such as /success-criteria docs/plan.md. The Skill reads the plan and codebase, classifies each requirement, and writes a structured qa-checklist.yaml with automated and code-audit checks.

What is the difference between automated and code-audit checks?▼

Automated checks run a command and compare output using exact, regex, numeric, or exit_code modes, such as curl status checks or build commands. Code-audit checks require reading specific source files to verify logic like conditional rendering or event handlers.

How do I update an existing qa-checklist.yaml when scope changes?▼

The Skill auto-triggers on feedback like feature changes or bug reports and runs an incremental update. It preserves existing check IDs, archives removed checks instead of deleting them, and adds new checks with the next available ID per category.

Does this work for LLM or agent-based features?▼

It produces the deterministic definition of done for any feature. For probabilistic surfaces like LLM calls or agents, it hands off to /ai-done, which reuses the checklist as its deterministic layer and adds eval bands, tripwires, and rollback procedures.

Why do checks need a side_effects flag?▼

Checks that write to databases, call paid external APIs, or mutate state are marked side_effects: true. The QA checklist loop runs these once at the end, outside the retry loop, preventing data pollution and wasted API credits.