What is the difference between Verification and Validation in this skill?

Verification (VER) focuses on whether the product meets technical specifications (built correctly) through tests and reviews, while Validation (VAL) ensures it meets actual user needs (built the right thing) through stakeholder approval.

How does this skill handle ineffective code reviews?

It identifies 'Rubber Stamp' reviews as an anti-pattern and provides a checklist-based approach along with social dynamics playbooks to ensure reviews are thorough and accountable.

What are the test coverage requirements for CMMI Level 3?

Level 3 projects require at least 70% test coverage for critical paths, mandatory automated testing in CI pipelines, and documented test strategies.

When is it acceptable to ship code without tests?

Shipping without tests is only allowed during production outages via the TEST-HOTFIX protocol, which requires documented justification and mandatory retrospective tests within 48 hours.

Does this skill provide code for specific testing frameworks?

No, this skill focuses on the engineering process and strategy. For framework-specific implementation like PyTest or Jest, you should use domain-specific engineering skills.

Quality Assurance & SDLC Engineering

概要

This skill provides a structured framework for Quality Assurance within the software development life cycle, specifically focusing on the critical distinction between Verification ("Did we build the product right?") and Validation ("Did we build the right product?"). It guides developers through CMMI-based quality levels, establishing mandatory test coverage, peer review standards, and user acceptance testing (UAT) protocols. By integrating this skill, Claude helps teams move beyond basic unit testing toward a mature QA strategy that prevents "test-last" anti-patterns and ensures high-quality releases through data-driven defect management and stakeholder validation.

主な機能

Distinguishes between technical Verification (tests) and stakeholder Validation (UAT)
Defines emergency exception protocols for mandatory retrospective testing (TEST-HOTFIX)
10 GitHub stars
Provides level-based QA requirements from Level 2 Managed to Level 4 Quantitatively Managed
Identifies common QA anti-patterns like Rubber Stamp Reviews and the Ice Cream Cone pyramid
Establishes clear metrics for review effectiveness and defect escape rates

ユースケース

Improving peer review effectiveness to catch defects before they reach production environments
Defining a comprehensive test strategy and coverage requirements for high-stakes projects
Implementing formal User Acceptance Testing (UAT) to ensure features meet actual user requirements

概要

主な機能

Distinguishes between technical Verification (tests) and stakeholder Validation (UAT)
Defines emergency exception protocols for mandatory retrospective testing (TEST-HOTFIX)
10 GitHub stars
Provides level-based QA requirements from Level 2 Managed to Level 4 Quantitatively Managed
Identifies common QA anti-patterns like Rubber Stamp Reviews and the Ice Cream Cone pyramid
Establishes clear metrics for review effectiveness and defect escape rates

ユースケース

Improving peer review effectiveness to catch defects before they reach production environments
Defining a comprehensive test strategy and coverage requirements for high-stakes projects
Implementing formal User Acceptance Testing (UAT) to ensure features meet actual user requirements