sddl-qa-review

Reviews execution stages or completed changes and produces a qa-report.md with verdict and next action.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill sddl-qa-review-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sddl-qa-review
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/sdd-lite/skills/sddl-qa-review
Command: npx skills add https://github.com/nico0695/ai-tools --skill sddl-qa-review-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides a unified, read-only QA review stage for the sdd-lite workflow, replacing ad-hoc quality checks with a structured report containing findings, evidence, verdict, and the safest next action. ## Core Features & Use Cases - Dual review modes: Run stage mode for a bounded review of one execution stage, or final mode for change-wide closeout review. - Evidence-based verdicts: Produces pass, pass_with_warnings, or fail verdicts grounded in spec.md, plan.md, execution-log.md, and actual repo state. - State synchronization: Updates state.yaml with QA summary, lifecycle status, open risks, and recommended next stage; only a clean final pass may mark a change completed. - Use Case: After an implementation stage finishes, trigger this stage to validate the changed files against acceptance criteria, run targeted checks, and decide whether to continue, correct, or close the change. ## Quick Start Ask the sddl orchestrator to run a QA review of the latest execution stage or a final closeout review for the active change.

Frequently Asked Questions about sddl-qa-review

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

FAQPage Schema
How do I run a QA review on a spec-driven development change?▼

Invoke the sddl-qa-review stage through the sddl orchestrator after an execution stage completes or at closeout. It reads the change artifacts, runs proportionate validation checks, and writes qa-report.md with a verdict and next action.

What is the difference between stage mode and final mode in QA review?▼

Stage mode reviews one bounded execution stage with targeted checks and never closes the change. Final mode reviews the whole implemented change using config.yaml quality commands and is the only mode that can mark a change completed on a clean pass.

Can the QA review stage modify code to fix findings?▼

No. The stage is strictly read-only with respect to application code, tests, configs, and planning artifacts. It only writes qa-report.md and updates state.yaml; corrections are routed back to execution or replanning stages.

What happens when a final QA review fails or has warnings?▼

A fail verdict sets lifecycle_status to blocked and routes toward correction or replanning. A pass_with_warnings verdict keeps the change in reviewing status and may create a final_review checkpoint requiring explicit user acceptance before closeout.

When does the QA review return blocked instead of a verdict?▼

It returns blocked when required artifacts like proposal.md, spec.md, plan.md, or execution-log.md are missing, when the review target cannot be identified safely, or when tooling failures prevent a trustworthy review.