qa-test-plan

Generate QA test plans with test cases, priorities, and acceptance criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/4asaanAI/Claude-patches --skill qa-test-plan-4asaanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-test-plan
Source: https://github.com/4asaanAI/Claude-patches/tree/main/framework-foundry/Claude%20Plugins/layaa-ai/skills/qa-test-plan
Command: npx skills add https://github.com/4asaanAI/Claude-patches --skill qa-test-plan-4asaanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams produce structured QA test plans that reduce missed regressions, unclear acceptance criteria, and uncoordinated testing during feature or release delivery.

Core Features & Use Cases

  • Test Scope & Objectives: Define scope, in-scope/out-of-scope items, and clear success criteria.
  • Test Types & Test Cases: Generate functional, regression, edge case, and acceptance test cases with priorities and expected outcomes.
  • Execution, Traceability & Responsibilities: Specify environments, test data, schedules, entry/exit criteria, and mapping of tests to requirements for cross-functional execution.
  • Use Case: For a payment checkout feature release, produce a prioritized test matrix, acceptance criteria, regression subset, and a test execution timeline for the release window.

Quick Start

Create a QA test plan for the "checkout v2" feature covering functional, regression, edge cases, acceptance criteria, required test environments, roles, and a two-week execution schedule.

Frequently Asked Questions about qa-test-plan

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

FAQPage Schema
How do I create a QA test plan for a software feature release?

To create a QA test plan, define the test scope, generate functional and regression test cases, establish acceptance criteria, and map traceability to requirements for cross-functional execution schedules.

What should be included in acceptance criteria and regression testing for sprint deliverables?

Acceptance criteria and regression testing should include prioritized test matrices, expected outcomes, edge case scenarios, required test environments, and clear entry and exit criteria for the release window.

How do I structure test cases with priorities for cross-functional teams?

Structure test cases by assigning priority levels to functional, regression, edge case, and acceptance tests, then map them to specific requirements and assign execution responsibilities across cross-functional teams.

Can I generate a test execution schedule and test data requirements for hotfix rollouts?

Yes, you can generate a test execution timeline specifying environments and test data requirements, specifically tailored for hotfix rollouts and sprint deliverables to ensure coordinated testing.

Does this approach work for defining in-scope and out-of-scope items in a testing strategy?

Yes, defining in-scope and out-of-scope items is a core part of the testing strategy, ensuring teams establish clear success criteria and test objectives before executing functional and acceptance tests.

What is the best way to map test traceability to requirements during release delivery?

The best way to map traceability to requirements is by aligning each generated test case and acceptance criterion directly with the sprint deliverable or feature requirement to ensure complete test coverage.