qa_test_plan

Generate QA test plans and coverage matrices from PRD/UX documentation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/denish12/codex-ai-agent-and-skills --skill qa-test-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa_test_plan
Source: https://github.com/denish12/codex-ai-agent-and-skills/tree/main/locales/en/.agents/skills/qa_test_plan
Command: npx skills add https://github.com/denish12/codex-ai-agent-and-skills --skill qa-test-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a comprehensive QA test plan and coverage matrix from PRD/UX documentation, reducing manual effort and ensuring consistent testing scope.

Core Features & Use Cases

  • Structured test plan generation from PRD/UX, including scope, assumptions, and entry/exit criteria.
  • Coverage matrix mapping flows to test cases and prioritization.
  • Outputs templates for CI-ready documentation and artifact generation.
  • Use Case: Given a PRD for a checkout flow, generate a test plan with 3 suites and 20 test cases.

Quick Start

Provide your PRD/UX reference and any preferred flows to generate a ready-to-use QA test plan.

Frequently Asked Questions about qa_test_plan

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

FAQPage Schema
How do I generate a QA test plan from PRD and UX documentation?

To generate a QA test plan from PRD and UX documentation, provide your reference specs to outline testing scopes, assumptions, entry and exit criteria, and map UI flows to test suites automatically.

What is a coverage matrix in QA testing and how is it structured?

A coverage matrix in QA testing maps UI flows to specific test cases and risk prioritization levels. It structures test suites by linking acceptance criteria directly to executable test scenarios.

Can I automate acceptance criteria mapping for a checkout flow?

Yes, you can automate acceptance criteria mapping for a checkout flow by processing PRD inputs to generate structured test suites with specific test cases and risk-based prioritization.

What's the best way to outline entry and exit criteria for software testing?

The best way to outline entry and exit criteria for software testing is to extract scope boundaries and assumptions directly from PRD and architecture docs to ensure consistent testing coverage.

Do I need architecture docs to create a CI-ready test plan?

You do not strictly need architecture docs, but providing them alongside PRD and UX specs enables more comprehensive test plan generation and coverage matrix mapping for CI-ready documentation.

Why does automated test plan generation improve coverage mapping?

Automated test plan generation improves coverage mapping by reducing manual effort and ensuring consistent testing scope across all PRD and UX defined UI flows and acceptance criteria.