qa-plan

Name: qa-plan
Availability: InStock
Author: kay6198835

Generate QA plans from GDDs and story files with test type classification.

Updated Feb 8, 2024

Search Tags:#automation #qa #stories #sprint #gdd #test-plan #manual-testing

Ready to run

npx skills add https://github.com/kay6198835/Game-RPG --skill qa-plan-kay6198835

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate comprehensive QA plans for sprints, features, or individual stories by reading GDDs and story files and classifying stories by test type (Logic/Integration/Visual/UI).

Core Features & Use Cases

Parse scope from sprint/feature/story input and flag missing referenced files as MISSING.
Classify stories by type and produce an integrated test plan covering automated tests, manual tests, smoke scope, and playtest sign-off.
Load supporting context from design/gdd indexes and per-GDD Acceptance Criteria and Formulas to ground test requirements.
Output a production-ready QA plan document with clear sections and file paths.

Quick Start

Provide the sprint/feature/story scope to qa-plan and run the plan generation to produce a production-ready QA plan document.

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 for a sprint or feature?▼

Generate a comprehensive QA test plan by providing a sprint, feature, or story scope argument. The tool reads GDDs and story files, classifies stories by test type, and outputs a structured document covering automated tests, manual verification, and smoke scope.

What types of testing are covered when planning QA for a sprint?▼

Sprint QA planning covers Logic, Integration, Visual, and UI test classifications. The generated plan integrates these types across automated tests, manual verification, smoke scope, and playtest sign-off sections.

How does QA planning handle missing story files or references?▼

Missing referenced files are recorded as MISSING without failing the plan generation. This allows the QA plan to process available sprint or feature scope while clearly flagging incomplete references for follow-up.

Can I create a manual testing plan from GDD acceptance criteria?▼

Yes, the QA plan loads supporting context from design/gdd indexes and per-GDD Acceptance Criteria and Formulas to ground test requirements. This context drives the manual verification and playtest sign-off sections of the output document.

Do I need a systems index file to generate a test plan for a feature?▼

A systems index file is not required but is loaded when available to provide supporting context. The tool reads design/gdd/systems-index.md to ground test requirements, but missing files are flagged as MISSING without failing the plan.

What is the best way to scope automated tests for individual stories?▼

Scope automated tests by providing a story path argument to the QA plan. This reads the specific story file and its referenced GDDs, classifies it by test type, and outputs targeted automated test requirements and smoke scope.