skills.rest
mbaho10
mbaho10COMMUNITY
Explore all skills by this author →
GitHub

qa-verify

Verify software stories against acceptance criteria and report PASS/FAIL evidence.

Updated Aug 27, 2026
Search Tags:#qa#verification#test-driven#adversarial#acceptance-criteria#defect-reporting#reproducible-evidence
One-click install
npx skills add https://github.com/mbaho10/claude-code-skills-9arm-workspace --skill qa-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-verify
Source: https://github.com/mbaho10/claude-code-skills-9arm-workspace/tree/main/.claude/skills/qa-verify
Command: npx skills add https://github.com/mbaho10/claude-code-skills-9arm-workspace --skill qa-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial verification of a built story against its acceptance criteria to ensure defects are found, not assumed correct.

Core Features & Use Cases

  • Explicit, criterion-by-criterion verification: each acceptance criterion is exercised and reported as PASS or FAIL with reproducible evidence.
  • Read-only evaluation: finds and reports defects without making fixes, preserving separation of roles.
  • Repro-driven defect discovery: pushes bad inputs and corner cases to reveal failures before users encounter them.

Quick Start

Provide the completed story and its acceptance criteria to run an adversarial QA pass and generate a reproducible PASS/FAIL report.

Frequently Asked Questions about qa-verify

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

FAQPage Schema
How do I verify story acceptance criteria before a sprint handoff?▼

Adversarial QA verifies software stories by exercising each acceptance criterion with bad inputs and corner cases to reveal defects. It generates a PASS/FAIL report with reproducible evidence for sprint completion.

What is adversarial verification in test-driven development?▼

Adversarial QA is a verification method that probes software with bad inputs and corner cases to find defects rather than assuming correctness. It enforces explicit acceptance criteria and reproducible test steps during QA cycles.

Can I use this to automatically fix defects found during QA cycles?▼

No, this performs read-only evaluation to find and report defects without making fixes. It preserves role separation by outputting a PASS/FAIL report with reproducible evidence instead of modifying code.

How do I generate reproducible evidence for a failed acceptance criterion?▼

Provide the completed story and its acceptance criteria to run an adversarial QA pass. It exercises each criterion and outputs a PASS/FAIL report containing reproducible evidence for any discovered defects.

Does this approach work for validating feature handoffs without dependencies?▼

Yes, this operates with no external dependencies to validate feature handoffs. It enforces explicit acceptance criteria to ensure defects are explicitly found and reported before users encounter them.

Related Skills

Explore More Software Engineering Skills→
ilandahanilandahan
9

QA & Ship Phase Skill

Validates acceptance criteria and generates release notes and deployment artifacts.

Community
Advanced
babywormbabyworm
43

code-review-policy

Classify LLM-generated code review findings into severity-labeled reports with reproducible evidence.

Community
Intermediate
laraxotlaraxot
26

bmad-testarch-atdd

Generate failing acceptance tests before implementation using the TDD cycle.

Official
Advanced
adolfoaranaes12adolfoaranaes12
2

trace-requirements

Generate bidirectional traceability matrices mapping acceptance criteria to implementation evidence and tests.

Community
Advanced