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.