skills.rest
labs21-dev
labs21-devOFFICIAL
Explore all skills by this author →
GitHub

qa

Reproduce final implementation state and validate against SPEC acceptance criteria.

28|2|Updated Feb 5, 2026
Search Tags:#qa#verification#audit#spec#reproduction#acceptance-criteria#workstream
One-click install
npx skills add https://github.com/labs21-dev/agents-stack --skill qa-labs21-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/labs21-dev/agents-stack/tree/main/templates/.agents/skills/using-agents-stack/qa
Command: npx skills add https://github.com/labs21-dev/agents-stack --skill qa-labs21-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA focuses on reproducing the final state and verifying compliance with SPEC acceptance criteria, surfacing gaps and edge cases before release.

Core Features & Use Cases

  • Fresh-session disjoint evaluation that is separate from implement discussions and reviews
  • SPEC-focused reproduction of CONSTITUTION.md, spec.md, plan.md, tasks.md, and handoff.md to generate a repeatable QA artifact
  • Structured QA reporting that yields qa-report.md and status.json for traceability

Quick Start

Run a fresh QA session against the current workstream by loading CONSTITUTION.md, spec.md, plan.md, tasks.md, and handoff.md, then generate a qa-report.md.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I verify implementation compliance against spec acceptance criteria?▼

Spec verification reproduces the final implementation state and validates it against acceptance criteria defined in spec.md. It surfaces gaps and edge cases before release to ensure full compliance with the defined specifications.

How do I generate a reproducible QA report for a software workstream?▼

Generating a QA report requires loading CONSTITUTION.md, spec.md, plan.md, tasks.md, and handoff.md in a fresh session. The process evaluates the implementation disjointly from development to output a structured qa-report.md and status.json.

What is adversarial verification in software engineering?▼

Adversarial verification is a fresh-session disjoint evaluation that separates implementation discussions from compliance reviews. It reproduces the final state and aggressively validates it against SPEC acceptance criteria to uncover hidden gaps and edge cases.

Does QA verification work without a handoff.md file?▼

QA verification validates workstreams defined by CONSTITUTION.md, spec.md, plan.md, tasks.md, and handoff.md. Missing handoff.md may limit the reproducibility and traceability of the generated qa-report.md and status.json outputs.

Why should I run QA verification in a fresh session instead of during implementation?▼

Running verification in a fresh session ensures a disjoint evaluation separate from implementation discussions and reviews. This adversarial approach prevents confirmation bias and effectively surfaces compliance gaps against the SPEC acceptance criteria.

Related Skills

Explore More Software Engineering Skills→
labs21-devlabs21-dev
28

release

Archive completed workstreams with PASS QA verdicts and update changelog and status records.

Official
Intermediate
labs21-devlabs21-dev
28

using-agents-stack

Coordinate goal-QA pipeline phases with file-based state and status.json gates.

Official
Advanced
prime-radiant-incprime-radiant-inc
91

subagent-driven-development

Dispatch fresh subagents per task with two-stage spec and code quality reviews.

Official
Advanced
srulytsrulyt
2

ralph-verification

Assesses whether code meets acceptance criteria and passes tests.

Community
Advanced