qa-verification-planner

Generates ISTQB-aligned test plans, TEST-* cases, and bidirectional coverage matrices from functional requirements and acceptance criteria.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill qa-verification-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-verification-planner
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/qa-verification-planner
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill qa-verification-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes ambiguity in how functional requirements and acceptance criteria are verified by providing a structured, auditable approach to test planning, design, and evidence management so teams can ensure coverage and release readiness.

Core Features & Use Cases

  • Test planning & strategy: Define scope, test levels, and risk-prioritized coverage targets aligned with ISTQB principles.
  • Test design & traceability: Produce TEST-* cases and a bidirectional coverage matrix mapping REQ → AC → TEST.
  • Evidence organization: Standardize storage and sign-off artifacts in execution-plan/reports/verification for audit and release.
  • Use Case: Given acceptance criteria for a user story, generate a test plan, test cases, coverage matrix, and an evidence folder ready for execution and sign-off.

Quick Start

Run the qa-verification-planner with the story's acceptance criteria and optional architecture or existing tests to produce a test plan, TEST-* cases, and a coverage matrix.

Frequently Asked Questions about qa-verification-planner

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

FAQPage Schema
How do I generate test cases from acceptance criteria?

Test planning for functional requirements involves defining scope, test levels, and risk-prioritized coverage targets aligned with ISTQB principles to ensure comprehensive verification and release readiness.

How do I create a bidirectional traceability matrix for requirements?

Create a bidirectional traceability matrix by mapping REQ → AC → TEST, enforcing bidirectional links between functional requirements, acceptance criteria, and generated test cases to guarantee coverage and auditability.

Does this verification approach align with ISTQB test design principles?

Yes, the verification approach aligns with ISTQB test design principles by applying standardized taxonomy across unit, integration, system, and acceptance testing levels to structure your test artifacts.

What's the best way to organize test evidence for audit and release sign-off?

To design a verification strategy, input your functional requirements and acceptance criteria to generate a structured test plan, TEST-* cases, and a coverage matrix covering unit, integration, system, and acceptance testing.

Can I use this for system and acceptance testing levels?

Yes, you can use this for system and acceptance testing levels, as it applies ISTQB-aligned taxonomy to produce test plans and coverage matrices across unit, integration, system, and acceptance testing.