skills.rest
naxoruto
naxorutoCOMMUNITY
Explore all skills by this author →
GitHub

qa-plan

Generate structured QA plans from GDDs and story files.

Updated Aug 23, 2026
Search Tags:#automation#planning#testing#qa#stories#gdd
One-click install
npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill qa-plan-naxoruto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/naxoruto/TE-limonchero-3d/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill qa-plan-naxoruto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA planning for sprints and features is time-consuming and error-prone when done manually. This skill quickly generates a comprehensive QA plan by reading GDDs and story files, classifying stories by test type, and outlining automated tests, manual test cases, smoke tests, and playtest requirements.

Core Features & Use Cases

  • Reads GDDs and story files to understand scope and acceptance criteria.
  • Classifies each story by test type (Logic, Integration, Visual/UI) and aggregates a cohesive plan.
  • Outputs a structured QA plan detailing automated tests, manual checks, smoke scope, and sign-off requirements.
  • Supports sprint-level planning before implementation to prevent post-mortem debugging.

Quick Start

Provide the sprint or feature scope (e.g., sprint name, feature system name, or story path) to generate the full QA plan.

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 game design documents and user stories?▼

Generating a QA test plan from game design documents involves reading GDDs and story files to classify stories by test type, then outlining automated tests, manual cases, and smoke scope. The output is a structured plan ready for hand-off.

What is the best way to classify user stories for sprint testing?▼

Classifying user stories for sprint testing means categorizing each story into Logic, Integration, or Visual/UI test types. This aggregates a cohesive plan detailing automated tests, manual checks, and smoke test scope.

When should I run QA planning for a new feature sprint?▼

QA planning for a new feature sprint should run before sprint implementation begins. Generating the plan beforehand prevents post-release QA overload by defining test scope and playtest sign-off requirements early.

Can I scope QA planning to a single feature system instead of a full sprint?▼

Scoping QA planning to a single feature system is fully supported alongside sprint-level or individual story paths. You provide the feature system name to get a targeted QA plan detailing automated tests and manual checks.

Does automated QA planning require external testing frameworks or dependencies?▼

Automated QA planning using this approach requires no external testing frameworks or dependencies. It reads your GDDs and story files to outline automated tests and manual cases without connected components.

Related Skills

Explore More Software Engineering Skills→
emcconnellemcconnell

qa-plan

Generate structured QA test plans from story files and GDDs.

Community
Advanced
Euraika-LabsEuraika-Labs
14

qa-plan

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

Official
Advanced
scomofoscomofo

qa-plan

Generate requirement-based QA plans from Godot story files and GDD criteria.

Community
Advanced
FrancisVargaFrancisVarga

qa-plan

Generate structured QA test plans from story files and GDD acceptance criteria.

Community
Advanced