qa

Validates implemented features against PRD and TRD specs with an 80% coverage gate.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill qa-asengardeon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/asengardeon/btt-sdd-pipeline/tree/main/plugins/btt-sdd/skills/qa
Command: npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill qa-asengardeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After code review approves a feature, teams still need objective proof that the implementation matches the PRD/TRD and meets test coverage thresholds. This Skill runs stage 5 of the SDD pipeline by invoking the qa-engineer agent to produce a formal QA report (specs/<slug>/qa-report.md) with a clear approved/rejected verdict. ## Core Features & Use Cases - Spec-based validation: Checks the implementation against the PRD and TRD, enforcing the 80% coverage gate before a feature can advance. - Git workflow safety: Handles retroactive reviews of already-merged PRs, rebases stale branches onto main, and resolves conflicts in review artifact files. - Timing and audit logging: Records invocation duration in specs/<slug>/timing-log.md and routes rejected features back to implementation with findings. - Use Case: After /btt-sdd:code-review approves a feature branch, run this Skill to generate qa-report.md; if approved, the pipeline proceeds to the security review stage. ## Quick Start Run the QA stage for the current feature slug to validate it against the PRD and TRD and generate the qa-report.md verdict.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run QA validation on a feature in an SDD pipeline?▼

Invoke this Skill after code review approves the feature. It locates the feature slug, verifies an approved code-review.md exists, then launches the qa-engineer agent to validate the implementation against the PRD and TRD and write specs/<slug>/qa-report.md.

What test coverage threshold does the QA stage enforce?▼

The QA stage enforces an 80 percent coverage gate. The qa-engineer agent runs the test suite and coverage tooling before issuing any verdict, and features below the threshold are rejected back to the implementation stage.

Can I run QA review on a PR that was already merged?▼

Yes. For retroactive reviews of merged PRs, the Skill creates a fresh branch from origin/main, produces only the qa-report.md for that round, and opens its own PR without additional gates, following the documented git workflow.

What happens when a feature fails the QA review?▼

A rejected feature returns to the implementation stage with the findings listed in qa-report.md. The recommended path is resuming the same implementing agent via SendMessage for small, targeted fixes rather than starting a new agent.

Why must the qa-engineer agent run with worktree isolation?▼

Worktree isolation prevents two agents from sharing the same working directory during concurrent pipeline activity. It is a mandatory default for this invocation, not a case-by-case condition, to avoid silent cross-contamination of changes.