skills.rest
nahisaho
nahisahoCOMMUNITY
Explore all skills by this author →
GitHub

quality-assurance

Define QA strategy, test plans, and quality metrics for software projects.

12|2|Updated Nov 26, 2025
Search Tags:#QA#metrics#traceability#test-strategy#test-planning
One-click install
npx skills add https://github.com/nahisaho/CodeGraphMCPServer --skill quality-assurance-nahisaho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-assurance
Source: https://github.com/nahisaho/CodeGraphMCPServer/tree/main/.claude/skills/quality-assurance
Command: npx skills add https://github.com/nahisaho/CodeGraphMCPServer --skill quality-assurance-nahisaho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines QA strategy, test planning, and quality metrics to ensure software quality throughout the lifecycle.

Core Features & Use Cases

  • QA Strategy: Define goals, KPIs, and acceptance criteria.
  • Test Planning: Scope, schedules, resources, and risk management.
  • Quality Metrics: Coverage, defect density, MTTR, etc.
  • Traceability: Map requirements to tests and verify coverage.

Quick Start

Create a QA strategy and a basic test plan for a new feature set.

Frequently Asked Questions about quality-assurance

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

FAQPage Schema
How do I create a QA strategy and test plan for my software project?▼

A QA strategy defines quality goals, KPIs, and acceptance criteria upfront. Test planning then establishes scope, schedules, resource allocation, and risk-based prioritization to govern testing throughout the lifecycle. Together they ensure systematic coverage and measurable quality outcomes from requirements through release.

What's the best way to trace requirements to test cases and verify coverage?▼

Requirements traceability maps each requirement to specific test cases, confirming no gaps exist between what's specified and what's validated. This bidirectional linkage catches unverified requirements and orphaned tests, ensuring acceptance criteria are formally verified before release.

How do I set up quality metrics like defect density and MTTR to track improvements?▼

Quality metrics quantify testing effectiveness and software health: defect density measures bugs per unit size, MTTR tracks repair speed, and coverage metrics show test scope. Establishing baselines and targets creates accountability and reveals where quality governance is strongest or weakest.

Can I use risk-based prioritization to focus testing on high-impact areas?▼

Risk-based test prioritization allocates effort where failure impact is highest and probability greatest. It concentrates resources on critical functionality and dependencies rather than uniform coverage, accelerating release readiness while protecting against the most damaging defects.

What do I need to define before starting formal test planning?▼

Before test planning, establish QA strategy goals, stakeholder roles, acceptance criteria, and risk profiles for the project. These inputs frame scope decisions, resource needs, and scheduling so the test plan aligns with business objectives and constraints.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
adolfoaranaes12adolfoaranaes12
2

trace-requirements

Generate bidirectional traceability matrices mapping acceptance criteria to implementation evidence and tests.

Community
Advanced
adityaarsharmaadityaarsharma
2

orbit-qa-regression-pack

Manage regression test suites with Playwright and CI pipelines.

Community
Advanced
ChoiHyunjinChoiHyunjin

agile-cycle-trading

Execute agile development cycles for trading applications with risk validation.

Community
Advanced