qa-strategy

Generate a QA strategy artifact with test matrices, UAT criteria, regression scenarios, and observability guidelines.

1|Updated Apr 2, 2026

Search Tags:#qa #observability #traceability #quality-gates #test-matrix #uat-criteria #regression-scenarios

Ready to run

npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill qa-strategy-anjinmeili

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-strategy
Source: https://github.com/AnjinMeili/Claude-ITIL-Planner/tree/main/planitil/skills/qa-strategy
Command: npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill qa-strategy-anjinmeili

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning quality assurance for software projects is prone to gaps and delays. This skill generates a complete QA strategy artifact that anchors test planning to SPEC.md, ARCH.md, and DEV-SPEC.md, ensuring traceability from requirements through tests to deployment.

Core Features & Use Cases

Generates a Test Matrix from ARCH.md components with defined test Type, Tool, Coverage Target, and Owner.
Derives UAT Criteria directly from SPEC.md acceptance criteria with explicit traceability.
Defines Regression Scenarios to capture the most critical, non-negotiable behaviors.
Specifies Observability and logging expectations to support operations and incident response.
Produces a cohesive QA.md that serves as the gating document between Layer 1 artifacts and release.

Quick Start

Invoke qa-strategy after SPEC.md, ARCH.md, and DEV-SPEC.md are confirmed to produce QA.md containing the Test Matrix, UAT Criteria, Regression Scenarios, and Observability Specification.

Frequently Asked Questions about qa-strategy

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

FAQPage Schema

How do I generate a QA strategy from software requirements and architecture specs?▼

To generate a QA strategy, you need to codify test matrices, UAT criteria, regression scenarios, and observability guidelines directly from your SPEC.md, ARCH.md, and DEV-SPEC.md artifacts. This ensures traceability from requirements through tests to deployment.

What is the best way to create a test matrix from architecture documentation?▼

Creating a test matrix involves deriving components from ARCH.md and defining the test Type, Tool, Coverage Target, and Owner for each. This approach anchors test planning directly to your architectural components and ensures structured coverage.

Do I need SPEC.md and DEV-SPEC.md prerequisites before planning UAT criteria?▼

Yes, you need confirmed SPEC.md, ARCH.md, and DEV-SPEC.md prerequisites before generating UAT criteria. The system guarantees these upstream prerequisites exist and derives UAT criteria directly from SPEC.md acceptance criteria with explicit traceability.

How do regression scenarios and observability guidelines fit into a QA plan?▼

Regression scenarios and observability guidelines are core sections of a cohesive QA plan. Regression scenarios capture critical non-negotiable behaviors, while observability guidelines specify logging expectations to support operations and incident response.

Why does my QA planning lack traceability from requirements to release?▼

QA planning lacks traceability when test matrices and UAT criteria are not anchored to SPEC.md and ARCH.md. By generating a cohesive QA.md that serves as a gating document between Layer 1 artifacts and release, you ensure end-to-end traceability.

Can I use qa-strategy for projects without predefined acceptance criteria?▼

No, you cannot effectively use this approach without predefined acceptance criteria. The tool explicitly derives UAT criteria and test matrices from SPEC.md acceptance criteria and ARCH.md components, requiring these inputs to function correctly.