qa

Verify deliverables against SPEC, PLAN, tests, and standards.

3|1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/zazzcode/zazz-skills --skill qa-zazzcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/zazzcode/zazz-skills/tree/main/.agents/skills/qa
Command: npx skills add https://github.com/zazzcode/zazz-skills --skill qa-zazzcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA actively finds issues and validates acceptance criteria via test-driven verification. When AC or TDD criteria are not met, it provides rework content to the human coordinator and creates a PR with full verification evidence once convergence is achieved.

Core Features & Use Cases

  • Verifies acceptance criteria across deliverables using SPEC, PLAN, tests, and standards
  • Generates actionable rework task content when criteria are not met
  • Produces reviewer-ready PR packages with full evidence
  • Supports owner coordination and sign-off for critical UX or spec gaps

Quick Start

Use qa to validate a deliverable against its SPEC, PLAN, tests, and standards and generate rework tasks when issues are found.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate test-driven verification against acceptance criteria?

Automated test-driven verification validates deliverables against SPEC, PLAN, acceptance criteria, tests, and project standards. It applies checks across unit, API, E2E, performance, and security layers to produce evidence and actionable rework tasks when gaps exist.

How do I generate a reviewer-ready PR package with full verification evidence?

Generating a reviewer-ready PR package requires completing verification across unit, API, E2E, performance, and security checks. Once convergence is achieved and all acceptance criteria are met, the PR package is produced with full verification evidence.

What should I do when acceptance criteria are not met during QA verification?

When acceptance criteria are not met during QA verification, actionable rework task content is generated and provided to the human coordinator. This process coordinates with the Deliverable Owner for sign-off where critical UX or spec gaps exist.

Can I coordinate with the deliverable owner for sign-off on critical spec gaps?

Yes, you can coordinate with the Deliverable Owner for sign-off when critical UX or spec gaps are found. The QA verification process actively identifies these gaps and facilitates owner coordination to ensure deliverable alignment.

Does test-driven verification work across unit, API, E2E, performance, and security checks?

Test-driven verification works across unit, API, E2E, performance, and security checks. It systematically applies project standards to each layer, producing comprehensive evidence and identifying specific areas requiring rework.

What's the best way to validate deliverables against SPEC and PLAN documents?

The best way to validate deliverables against SPEC and PLAN documents is through automated test-driven verification. This process cross-references the deliverable with acceptance criteria, tests, and project standards to produce actionable rework items or a verified PR package.