skills.rest
asengardeon
asengardeonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sdd-qa

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

Updated Aug 25, 2026
Search Tags:#code review#validation#qa#git worktree#pipeline#test coverage#spec-driven development
One-click install
npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill sdd-qa-asengardeon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-qa
Source: https://github.com/asengardeon/btt-sdd-pipeline/tree/main/.claude/skills/sdd-qa
Command: npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill sdd-qa-asengardeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After code review approves a feature, teams still need objective validation that the implementation actually satisfies the PRD and TRD requirements and meets the test coverage threshold. This Skill runs stage 5 of the SDD pipeline, invoking the qa-engineer agent to produce a formal QA report. ## Core Features & Use Cases - Spec-based validation: Invokes the qa-engineer agent with the PRD, TRD, and feature branch to produce specs/<slug>/qa-report.md from a template. - Coverage gate enforcement: Checks the 80% test coverage gate before issuing an approved/rejected verdict. - Git workflow safety: Handles retroactive QA on already-merged PRs, rebases stale branches onto main, isolates the agent in a git worktree, and logs invocation duration to timing-log.md. - Use Case: After /sdd-code-review approves a feature slice, run this Skill to objectively validate it against the spec; if rejected, the feature returns to /sdd-implement with the findings listed. ## Quick Start Run the /sdd-qa command for the current feature slug to validate the implementation against its PRD and TRD and generate the QA report.

Frequently Asked Questions about sdd-qa

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

FAQPage Schema
How do I run QA validation in a spec-driven development pipeline?▼

Run the /sdd-qa command after code review approves the feature. It invokes the qa-engineer agent with the PRD, TRD, and feature branch, producing specs/<slug>/qa-report.md with an approved or rejected verdict.

What test coverage threshold does the QA stage enforce?▼

The QA stage enforces an 80 percent test coverage gate. The qa-engineer agent runs the test suite and coverage checks before issuing any verdict in the qa-report.md file.

Can I run QA on a pull request that was already merged?▼

Yes. For retroactive review of a merged PR, create a new branch from origin/main, produce only the qa-report.md for that round, and open its own PR without additional gates, following the GIT-WORKFLOW.md retroactive review section.

What happens if the QA report rejects the feature?▼

A rejected feature returns to /sdd-implement with the findings listed. Prefer resuming the same implementing agent via SendMessage for small, targeted fixes rather than invoking a new agent.

Why must the qa-engineer agent run in a git worktree?▼

The worktree isolation prevents two agents from sharing the same working directory during concurrent invocations. It is a mandatory default for this call, not a case-by-case condition, per the GIT-WORKFLOW.md isolation rules.

Related Skills

Explore More Software Engineering Skills→
NSEvteevNSEvteev
31

review

Unify local branch and GitHub PR reviews into a single workflow.

Community
Advanced
nuoyanruoshuinuoyanruoshui
47

security-audit

Identify and prioritize security vulnerabilities in Godot game code and project data.

Community
Advanced
dpaola2dpaola2
3

pipeline-approve

Guide reviewers through pipeline checkpoint approvals and update artifacts with decisions.

Community
Advanced
UnsupervisedcomUnsupervisedcom
49

manual_tests

Automates DeepWork hook and rule tests across isolated sub-agents with enforced constraints.

Official
Basic