qa-plan

Name: qa-plan
Availability: InStock
Author: dnkrow

Generate QA test plans from sprint, feature, or story scopes.

1|Updated May 15, 2026

Search Tags:#acceptance criteria #test plan #qa planning #smoke testing #playtest sign-off #story triage #gdd validation

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes guesswork from planning QA by turning a sprint/feature/story scope into a concrete, structured test plan tied to real acceptance criteria and GDD requirements.

Core Features & Use Cases

Sprint/Feature/Story Scope Parsing: Build the plan from a sprint’s latest story list, an epic/feature’s stories, or a single story path, with interactive scope selection when no argument is provided.
Story Classification by Test Type: Automatically categorize stories into Logic, Integration, Visual/Feel, UI, or Config/Data based on acceptance criteria signals.
Test Allocation & Output Generation: Produce an end-to-end plan including automated test targets, manual checklists, smoke test scope, and playtest requirements when needed.

Quick Start

Run qa-plan with the argument sprint to generate a QA plan for the current sprint and write it to production/qa/.

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 test plan from sprint stories and GDD acceptance criteria?▼

A QA test plan for a sprint is generated by reading in-scope story files and GDD acceptance criteria, then classifying stories by test type. It outputs structured targets for automated tests, manual evidence, smoke checks, and playtest sign-off.

What is story triage in QA planning and how does test type classification work?▼

Story triage in QA planning categorizes stories into Logic, Integration, Visual/Feel, UI, or Config/Data based on acceptance criteria signals. This classification determines whether a story requires automated test targets or manual verification checklists within the test plan.

Can I build a test plan for a single story path or an epic glob instead of a full sprint?▼

Yes, you can build a test plan from a single story path or an epic/story glob. The tool supports scoped input resolution from sprint files, epic globs, and single-story paths, providing interactive scope selection when no specific argument is provided.

What's the best way to determine required automation vs manual verification for game features?▼

The best way to determine automation versus manual verification is to evaluate acceptance criteria signals during story classification. The tool allocates automated test targets for logic and integration, while visual/feel and UI stories receive manual checklists and playtest requirements.

Does the generated QA plan include smoke testing scope and playtest sign-off requirements?▼

Yes, the generated QA plan includes smoke testing scope and playtest sign-off requirements. The end-to-end plan allocates specific automated test targets, manual evidence checklists, smoke checks, and playtest sign-off criteria based on the parsed story scope.

Do I need a GDD with acceptance criteria to use sprint QA planning?▼

Yes, you need referenced GDD acceptance criteria and in-scope story files to use sprint QA planning. The tool reads these inputs to classify stories and generate the structured test plan, ensuring QA coverage is tied to real requirements rather than guesswork.