qa-plan

Generate structured QA test plans from story files and GDDs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA planning is often done after work begins, leaving teams unprepared for required automated tests, manual verification steps, and playtest sign-off. This Skill centralizes requirements by reading story files and referenced GDDs to produce a clear, actionable QA plan before development starts, reducing rework and missed test coverage.

Core Features & Use Cases

  • Scope parsing: Resolve scope from a sprint, feature, or single story and report missing story files without failing the plan.
  • Input extraction: Read story titles, acceptance criteria, implementation files, estimates, dependencies, and referenced GDD formulas and acceptance sections.
  • Classification & mapping: Classify stories as Logic, Integration, Visual/Feel, UI, or Config/Data and map each to automated test paths, manual checklists, smoke tests, and playtest requirements.
  • Output generation: Assemble a full QA plan Markdown file under production/qa with test summaries, automated test guidance, manual verification checklists, smoke scope, and Definition of Done gates.
  • Collaborative protocol: Conservatively classify ambiguous stories, flag missing GDDs, and require explicit user approval before writing the plan file.

Quick Start

Create a QA plan for the current sprint and write it to production/qa by asking: "Generate QA plan for sprint".

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 structured QA test plan for a sprint?

To generate a QA test plan for a sprint, the tool analyzes referenced story files, GDD acceptance criteria, and sprint metadata to classify stories and allocate testing work. It extracts acceptance criteria, maps tests to integration paths, and writes a markdown plan to production/qa.

What is story classification in QA planning?

Story classification in QA planning categorizes stories as Logic, Integration, Visual/Feel, UI, or Config/Data. This mapping directs each story to appropriate automated test paths, manual checklists, smoke tests, and playtest requirements for comprehensive coverage.

How do I map automated test paths to sprint stories?

You can map automated test paths by parsing story implementation file lists and GDD formulas. The generated QA plan matches classified stories to specific unit or integration test paths, defining required smoke and playtest verification steps.

Can I create a QA plan if some GDD acceptance criteria are missing?

Yes, you can create a QA plan with missing GDDs. The generation process conservatively classifies ambiguous stories, reports missing story files without failing, and explicitly flags missing GDDs for review before requiring user approval to write the plan.

What's the best way to define Definition of Done gates for a feature?

The best way to define Definition of Done gates is assembling a QA plan that consolidates test summaries, automated test guidance, manual verification checklists, and smoke scope from story files and GDD criteria into a single markdown file.