skills.rest
LordKuper
LordKuperCOMMUNITY
Explore all skills by this author →
GitHub

qa-plan

Generates a structured QA plan from sprint stories and GDD references.

Updated Mar 26, 2026
Search Tags:#automation#planning#testing#qa#sprint#gdd#playtest
One-click install
npx skills add https://github.com/LordKuper/agentic-game-studio --skill qa-plan-lordkuper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill qa-plan-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA planning for software projects is often tedious and error-prone; teams need a repeatable, structured method to turn sprint goals and GDD references into a complete test plan.

Core Features & Use Cases

  • Reads sprint scope and GDD references to identify all testable stories.
  • Classifies stories by test type (Logic, Integration, Visual/UI) and outlines required automated tests and manual verification.
  • Generates outputs including automated test scope, manual test cases, smoke-test scope, and playtest sign-off requirements.

Quick Start

Run qa-plan to generate a comprehensive QA plan for the current 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 plan from sprint stories?▼

You can generate a QA plan by reading in-scope sprint stories and their GDD references to classify tests into Logic, Integration, and Visual/UI categories, producing a complete test plan document for developer and QA team hand-off.

What is included in an automated testing scope for a software sprint?▼

An automated testing scope for a software sprint includes classified test mappings for Logic and Integration stories, outlining specific automated test requirements alongside manual verification cases, smoke-test scope, and playtest sign-off criteria.

How do I map GDD references to test cases for feature validation?▼

Mapping GDD references to test cases involves reading story inputs, classifying them by test type, and outlining validation criteria to ensure all feature requirements are covered by automated, manual, smoke-test, or playtest requirements.

Can I use this to outline manual test cases and smoke-test scope?▼

Yes, you can outline manual test cases and smoke-test scope by reading in-scope stories and their GDD references, generating a structured QA plan document that includes both automated and manual verification requirements.

Does this QA planning approach support playtest sign-off requirements?▼

Yes, this QA planning approach supports playtest sign-off requirements by generating a comprehensive QA plan document that includes playtest validation criteria alongside automated, manual, and smoke-test scope mappings.

Related Skills

Explore More Software Engineering Skills→
sethdfordsethdford
2

Sprint Planning Assistant

Generate sprint plans and risk assessments from team capacity and velocity.

Community
Advanced
levnikolaevichlevnikolaevich
534

ln-221-story-creator

Generate 8-section Story documents from IDEAL plans and export to Linear.

Community
Advanced
CENKSSSCENKSSS

qe-test-execution

Orchestrate test suite execution with parallel sharding, retries, and real-time results.

Community
Advanced
Euraika-LabsEuraika-Labs
14

qa-plan

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

Official
Advanced