qa-plan

Generate a QA plan from PRD, gameplan, architecture, and test coverage artifacts.

3|Updated Feb 18, 2026

Search Tags:#automation #planning #testing #quality assurance #documentation #qa

Ready to run

npx skills add https://github.com/dpaola2/pipeline-skills --skill qa-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/dpaola2/pipeline-skills/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/dpaola2/pipeline-skills --skill qa-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed Quality Assurance plans by consolidating information from various project artifacts, ensuring thorough testing without manual compilation.

Core Features & Use Cases

Consolidates Project Artifacts: Gathers data from PRD, gameplan, architecture proposals, test coverage matrices, and progress reports.
Identifies Manual Testing Needs: Extracts criteria not covered by automated tests and spec gaps.
Generates Actionable Test Scenarios: Creates step-by-step instructions for manual testers.
Use Case: After a feature is implemented, run this Skill to generate a complete QA plan that includes manual test cases, edge case scenarios, known limitations, and a rollback strategy, ready for the QA team.

Quick Start

Use the qa-plan skill to generate a QA plan for the project identified by 'SN-3'.

Frequently Asked Questions about qa-plan

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

FAQPage Schema

How do I generate a QA plan from project artifacts like PRD and architecture docs?▼

Generating a QA plan from project artifacts involves consolidating PRD, architecture, and test coverage data to identify manual testing requirements and ensure all acceptance criteria are covered by automated or manual tests.

How do I extract manual test cases from automated test coverage gaps?▼

Extracting manual test cases from coverage gaps requires analyzing test coverage matrices against acceptance criteria, then generating step-by-step instructions for scenarios not covered by automated tests.

Can I generate rollback procedures and edge case scenarios as part of a quality assurance plan?▼

Generating rollback procedures and edge case scenarios is supported by analyzing implementation progress and known limitations, producing actionable test scenarios that include rollback strategy for the QA team.

What is the best way to consolidate implementation progress and spec gaps into test data scenarios?▼

Consolidating implementation progress and spec gaps into test data scenarios is done by analyzing project artifacts to extract criteria not covered by automated tests, creating actionable manual test cases.

Does this QA plan generation approach work without specific testing framework dependencies?▼

Generating QA plans without specific testing framework dependencies is supported, as the skill analyzes project artifacts directly and requires no external dependencies to identify manual testing needs.

When should I not use automated QA plan generation for my testing documentation?▼

Automated QA plan generation may not suit projects lacking updated project artifacts like PRDs or architecture proposals, as the output quality depends on consolidating existing implementation progress and spec data.