qa-plan

Generate structured QA test plans from project story files and artifacts.

14|1|Updated Apr 12, 2026

Search Tags:#automation #qa #story #classification #sprint #gdd #testplan

Ready to run

npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill qa-plan-euraika-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/qa-plan
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill qa-plan-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual effort of crafting QA test plans by automatically reading stories, GDDs, and other project artifacts to produce a structured plan covering automated tests, manual checks, smoke scopes, and playtest sign‑offs.

Core Features & Use Cases

Automated Scope Parsing: Detects sprint, feature, or story scope and gathers relevant files.
Story Classification: Categorizes stories into Logic, Integration, Visual/Feel, UI, or Config/Data based on acceptance criteria.
Full Test Plan Generation: Creates comprehensive QA documents with test summaries, automated test specs, manual checklists, smoke test lists, and playtest requirements.
Use Case Example: Before a new sprint begins, run the skill to get a ready‑to‑share QA plan that aligns development and testing efforts.

Quick Start

Request the qa‑plan skill to create a test plan for the upcoming 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 QA test plan for a new sprint?▼

You can automate sprint test plan generation by parsing project story files, GDDs, and artifacts to classify story types and output a markdown document containing test summaries, automated test specs, manual checklists, and smoke test scope.

What is story classification in QA test planning?▼

Story classification in QA test planning categorizes project stories into Logic, Integration, Visual/Feel, UI, or Config/Data types based on acceptance criteria to outline required automated and manual tests.

How do I create manual checklists and smoke test scopes from GDDs?▼

You can create manual checklists and smoke test scopes by parsing GDDs and project artifacts to detect scope and generate a structured markdown document containing manual checklists, smoke test lists, and playtest sign-off requirements.

Can I automate test plan creation for features without manual effort?▼

Yes, you can automate test plan creation for features by parsing project artifacts to determine scope and produce a comprehensive QA document covering automated test specifications, manual checks, and playtest requirements.

What do I need to generate structured QA documents for playtest sign-off?▼

To generate structured QA documents for playtest sign-off, you need project story files, GDDs, and related artifacts available for parsing to determine scope and produce test summaries with sign-off requirements.

Does qa-plan work with game design documents?▼

Yes, qa-plan works with game design documents by parsing GDDs alongside story files to classify story types and outline required automated and manual tests within the generated test plan.