Quality Assurance

Validates implemented software stories with tests, code review, and quality gate assessment.

1|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/normcrandall/claudeskills --skill quality-assurance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Quality Assurance
Source: https://github.com/normcrandall/claudeskills/tree/main/qa
Command: npx skills add https://github.com/normcrandall/claudeskills --skill quality-assurance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides thorough quality assessment for implemented stories, ensuring compliance with coding standards and architectural patterns, and delivering clear quality gate decisions (PASS/CONCERNS/FAIL). It automates the review process, giving you confidence in your releases.

Core Features & Use Cases

  • Quality Gate Decisions: Generates formal quality gate decisions (PASS, CONCERNS, FAIL, WAIVED) with detailed rationale, issues, and recommendations.
  • Standards & Architecture Validation: Reviews implemented code against defined coding standards and architectural patterns to ensure consistency and maintainability.
  • Requirements Traceability: Maps acceptance criteria to test coverage, verifying that all requirements are adequately tested.
  • Risk Assessment: Assesses technical, integration, and testing risks, providing a summary of potential impacts.
  • Use Case: After a developer implements a story, invoke this skill with the story file to get a comprehensive QA report and a clear "PASS" or "FAIL" decision, streamlining your review process.

Quick Start

Validate a story implementation

Skill(command: "qa")

Provide story file path, e.g., "docs/stories/1.1.dark-mode-toggle.md"

Frequently Asked Questions about Quality Assurance

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

FAQPage Schema
How do I validate a completed software story against quality standards?

Quality assurance validates implemented stories by testing, code review, and quality gate assessment. Invoke the Skill with your story file to receive a comprehensive QA report with a formal decision—PASS, CONCERNS, or FAIL—based on coding standards, architectural compliance, and requirements traceability.

What does a quality gate decision include?

A quality gate decision documents the validation outcome with detailed rationale, identified issues, and recommendations. Decisions are marked PASS, CONCERNS, FAIL, or WAIVED, enabling confident release decisions and clear communication of blockers or risks.

Can quality assurance map acceptance criteria to test coverage?

Yes. Requirements traceability maps acceptance criteria to test coverage, verifying that all requirements are adequately tested and reducing gaps between specifications and implementation validation.

How does risk assessment factor into QA decisions?

Risk assessment evaluates technical, integration, and testing risks during validation. The QA report summarizes potential impacts alongside gate decisions, helping teams prioritize mitigation and make informed release choices.

What input does the quality assurance process need?

Provide a completed story file in markdown format containing implementation details, acceptance criteria, and code artifacts. The Skill reviews the story against defined coding standards and architectural patterns to generate test results and a QA report.