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/polsegu/Claude-Code-Game-Dev --skill qa-plan-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill qa-plan-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often skip creating a formal test strategy until after implementation, leaving developers without clear guidance on what to automate, what must be verified manually, and how to gate release readiness. This Skill ensures QA work is planned before development begins by turning story files and referenced GDDs into an actionable test plan.

Core Features & Use Cases

  • Scope resolution: Determine scope from a sprint, a named feature, or a single story and handle missing referenced files without failing the plan.
  • Automated extraction: Read story acceptance criteria and referenced GDD Formulas to derive testable requirements and file lists.
  • Classification & output: Classify stories into Logic, Integration, Visual/Feel, UI, or Config/Data, produce automated test paths, manual checklists, smoke test scope, and playtest sign-off rules.
  • Collaborative guardrails: Conservative classification rules, explicit AskUserQuestion fallback for scope, and a required user confirmation step before writing the plan to production.

Quick Start

Create a QA plan for the current sprint that lists automated tests, manual checklists, smoke test scope, and playtest requirements.

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 formulas?

Generate a QA test plan by reading story files and referenced Game Design Documents to extract acceptance criteria and formulas, classify tests, and assemble automated and manual test scopes. The output is a complete document suitable for saving to production.

What is the best way to classify game development tests into automated and manual scopes?

Classify game development tests by categorizing stories into Logic, Integration, Visual/Feel, UI, or Config/Data types. This classification produces distinct automated test paths and manual checklists to ensure comprehensive sprint coverage.

Can I create a QA plan for a single feature without failing on missing referenced files?

Yes, scope resolution handles a sprint, a named feature, or a single story, and processes missing referenced files without failing the plan. It uses conservative classification rules and an explicit fallback to ask for scope clarification.

How do I extract acceptance criteria to build a smoke test scope for a sprint?

Extract acceptance criteria automatically from story files to derive testable requirements and build a smoke test scope. The generated QA plan also includes playtest sign-off rules to verify release readiness before development concludes.

Does QA planning require user confirmation before writing the test plan to production?

Yes, QA planning requires a user confirmation step before writing the test plan to production. This collaborative guardrail ensures the extracted test scope and classified stories are verified before finalizing the document.