qa-plan

Generate structured QA plans from stories and GDD references.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill qa-plan-solace-ill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/solace-ill/vector-flow --skill qa-plan-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill generates a structured QA plan for a sprint, feature, or individual story by reading all in-scope story files and their referenced GDDs, classifying each story by test type, and producing a plan that tells developers exactly what testing work is required, including automated tests, manual verifications, smoke-test scope, and playtest sign-off requirements. Run before a sprint begins so the team knows upfront what testing work is required.

Core Features & Use Cases

  • Scope resolution: resolve sprint/feature/story scope using arguments or AskUserQuestion
  • Input loading: read stories and GDD/ADR references to extract acceptance criteria, estimates, and dependencies
  • Classification: assign a test type to each story
  • Output generation: produce a QA plan at production/qa/qa-plan-[sprint-slug]-[date].md
  • Gap handling: note missing files without failing the plan

Quick Start

Run qa-plan with a scope argument to generate a plan for a sprint, feature, or individual story.

Frequently Asked Questions about qa-plan

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

FAQPage Schema
How do I automate QA planning for a sprint?

Automate sprint QA planning by parsing in-scope stories and GDD references to generate a structured plan listing automated tests, manual verifications, smoke-test scope, and playtest requirements. Run the skill with a scope argument before the sprint begins to define all required testing work upfront.

What is included in a sprint QA plan?

A sprint QA plan includes classified test types for each story, specifically detailing required automated tests, manual verifications, smoke-test scope, and playtest sign-off requirements. It extracts acceptance criteria, estimates, and dependencies from story files and referenced GDDs to guide developers.

Can I generate a QA plan for a single feature or individual story?

Yes, QA plan generation applies to sprint-level planning, feature-level scoping, or individual stories. You can resolve the scope using arguments or interactive prompts to produce a targeted testing plan that lists the exact automated and manual verification work required.

What happens to the QA plan if a referenced GDD file is missing?

When a referenced GDD file is missing, the QA plan notes the file as MISSING instead of failing the generation process. This gap handling ensures the plan is still produced at production/qa/qa-plan-[sprint-slug]-[date].md, allowing the team to identify and address missing documentation.

How does the QA plan classify testing work for developers?

The QA plan classifies testing work by reading in-scope story files and referenced GDDs to assign a test type to each story. It categorizes the work into automated tests, manual verifications, smoke-test scope, and playtest requirements, telling developers exactly what testing actions are needed.

Do I need to manually check dependencies before generating a QA plan?

No manual dependency checking is required. The skill automatically loads stories and GDD/ADR references to extract acceptance criteria, estimates, and dependencies, resolving sprint, feature, or story scope seamlessly during the plan generation process.