quality

Performs independent verification, validation, and inspection to produce a release-blocking quality verdict.

4|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/douglance/sdlc-plugin --skill quality-douglance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality
Source: https://github.com/douglance/sdlc-plugin/tree/main/.rulesync/skills/quality
Command: npx skills add https://github.com/douglance/sdlc-plugin --skill quality-douglance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Passing tests alone do not prove a change is correct or meets the specification. This Skill provides an independent quality gate that judges whether the change is right, not just whether it runs, catching issues that dynamic tests miss. ## Core Features & Use Cases - Verification and Validation: Confirms tests pass, types check, and static analysis is clean, then validates the change satisfies the spec and the user's actual need. - Checklist-Based Review: Inspects diffs against a checklist covering error handling, boundaries, security, spec contradictions, missing tests, and maintainability. - Quality Attribute Assessment: Evaluates relevant "-ilities" such as performance, security, reliability, usability, and maintainability with measurable targets. - Use Case: Before a release, run this phase to produce a pass/fail verdict with findings ranked by severity, so release-blocking issues surface before deployment. ## Quick Start Use the quality skill to independently verify and validate this change against the specification and produce a quality verdict with findings by severity.

Frequently Asked Questions about quality

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

FAQPage Schema
How do I verify a code change beyond running tests?▼

Combine verification (tests pass, types check, static analysis clean) with validation that the change satisfies the spec and user need. Then review the diff against a checklist covering error handling, boundaries, security, and missing tests.

What is the difference between verification and validation in software quality?▼

Verification confirms the product was built right: tests pass, types check, static analysis is clean. Validation confirms the right thing was built: the change satisfies the specification and the user's actual need.

What should a code review checklist include before release?▼

A release review checklist should cover error handling, boundary conditions, security concerns, contradictions with the specification, missing tests, and maintainability. This inspection catches issues that dynamic tests do not exercise.

When should quality review run as an independent gate?▼

Run it as an independent gate when the review can proceed in parallel with other work, using a dedicated quality-engineer role. Otherwise perform the verification and validation locally within the current workflow.

Why is a green test suite not enough for release approval?▼

Tests only exercise paths they were written to cover and cannot prove the change matches the specification or user need. Inspection and validation against explicit criteria catch spec contradictions, missing tests, and quality attribute gaps.