qa-plan

Generate a QA plan document with test types, evidence requirements, and device matrix.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill qa-plan-cenconq25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill qa-plan-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often scramble to assemble a coherent plan from disparate sprint artifacts; this Skill streamlines and standardizes that work by generating a unified QA plan from PRDs, stories, and design context.

Core Features & Use Cases

  • Classifies each story by test type (Logic, Integration, Visual/Feel, UI, Config/Data) and maps them to automated or manual test plans.
  • Produces evidence requirements, smoke scope, a device matrix, and staffing estimates to guide sprint QA execution.
  • Creates a formal QA plan document and updates story metadata with Test Evidence references to ensure traceability.

Quick Start

Provide the sprint or feature details to generate the full QA plan and attach it to the affected stories.

Frequently Asked Questions about qa-plan

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

FAQPage Schema
How do I automate sprint QA planning from feature scope and stories?

Automate sprint QA planning by inputting sprint or feature details to generate a unified plan that classifies stories by test type, defines evidence requirements, and produces a device-matrix and smoke scope to guide testing activities.

What is the best way to classify sprint stories into automated or manual test plans?

Classify sprint stories by evaluating each against test type categories like Logic, Integration, Visual/Feel, UI, and Config/Data, then map them directly to corresponding automated or manual test plans within the generated QA documentation.

How do I generate a device matrix and smoke scope for cycle QA execution?

Generate a device matrix and smoke scope by providing sprint or feature details, which produces evidence requirements and staffing estimates to comprehensively guide cycle QA execution and testing activities.

Can I enforce structured QA documentation and update story metadata with test evidence references?

You can enforce structured QA documentation by producing a formal plan document, updating story metadata with Test Evidence references, and saving artifacts in the repository to ensure full traceability across the sprint.

Does this QA planning approach work with PRDs and design context from disparate sprint artifacts?

This QA planning approach works directly with PRDs, stories, and design context from disparate sprint artifacts, streamlining the assembly of a coherent and standardized unified QA plan from fragmented inputs.