qa-plan

Generate structured QA test plans from sprint stories and GDD sections.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents last-minute QA scramble by turning your sprint or feature scope (stories plus referenced GDDs) into a complete, structured QA plan covering automated tests, manual verification, smoke scope, and playtest sign-off expectations.

Core Features & Use Cases

  • Scope-driven plan generation: Builds QA plans for a sprint, feature, or single story by reading the appropriate story inputs.
  • Test-type classification: Automatically classifies stories into Logic, Integration, Visual/Feel, UI, or Config/Data using declared Type or inferred criteria.
  • GDD-aligned coverage: Extracts GDD sections (Acceptance Criteria, Formulas, Edge Cases) to ensure tests cover the actual requirements and boundary conditions, with explicit notes when GDD formula/edge sections are missing.
  • Actionable output format: Produces a ready-to-share plan including automated test file paths, manual checklists, smoke-test scope, and playtest requirements.

Quick Start

Run qa-plan with the argument "feature: <system-name>" to generate a QA plan for all stories in that system’s epic scope.

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

A QA test plan for game development prevents last-minute testing scramble by structuring coverage into automated tests, manual verification checklists, smoke test scope, and playtest sign-off needs based on your sprint scope and referenced GDD sections.

How does automated story classification work for QA test planning?

Automated story classification parses declared story types or infers them from criteria, sorting stories into Logic, Integration, Visual/Feel, UI, or Config/Data categories. This ensures the generated QA plan applies the correct testing approach to each story type.

Can I use GDD acceptance criteria and edge cases to build manual verification checklists?

Yes, GDD coverage works by extracting Acceptance Criteria, Formulas, and Edge Cases sections to ensure tests cover actual requirements and boundary conditions. The plan explicitly notes when GDD formula or edge case sections are missing.

What happens to QA plan generation when story files or GDD sections are missing?

When story files or GDD sections are missing, the tool applies conservative handling and explicitly notes missing GDD formula or edge case sections in the output. This ensures the generated QA plan remains production-ready while flagging coverage gaps.

Does the generated test plan include automated test file paths and smoke test scope?

Yes, the production-ready markdown output includes specific automated test file paths, manual verification checklists, smoke-test scope, and playtest sign-off requirements. The plan is generated at a specified path for immediate team distribution.

What is the best way to plan smoke tests and playtest sign-off for a game feature sprint?

Input sprint scope, feature epic, or single story files alongside referenced GDD sections to extract acceptance criteria and edge cases, producing classified story type inputs required for generating the QA test plan.