skills.rest
HechaoYannet
HechaoYannetCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa-plan

Generate structured QA plans from sprint stories and GDDs.

Updated Apr 8, 2026
Search Tags:#automation#story#sprint#gdd#test-plan#manual-testing#qa-plan
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill qa-plan-hechaoyannet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill qa-plan-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates a structured QA plan for a sprint, feature, or individual story. It reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI/Config/Data), and outputs a plan covering automated tests, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins to align the team on testing work and acceptance criteria.

Core Features & Use Cases

  • Parse scope from the sprint plan, a feature epic, or a specific story.
  • Load inputs from story files and referenced GDDs to extract acceptance criteria and implementation notes.
  • Classify each story by test type (Logic, Integration, Visual/Feel, UI, Config/Data).
  • Generate a complete QA plan document, including automated test recommendations, manual verification, smoke-test scope, and playtest requirements.
  • Output the plan to production/qa/qa-plan-[sprint-slug]-[date].md for traceability and hand-off.

Quick Start

Run the qa-plan with your current sprint scope to generate a complete 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 for a sprint and feature backlog?▼

A QA test plan is generated by parsing sprint scope and story files to extract acceptance criteria. The tool classifies stories by test type and outputs a structured plan covering automated tests, manual verification, and smoke test scope.

How does story classification by test type work for QA planning?▼

Story classification for QA planning works by reading story files and GDDs, then categorizing each story into Logic, Integration, Visual/UI, UI, or Config/Data test types to define the required automated and manual testing scope before coding begins.

Can I create a QA plan for a single individual story instead of a full sprint?▼

Yes, you can create a QA plan for an individual story. The tool parses scope from a specific story file, loads referenced GDDs for implementation notes, and outputs a targeted plan with manual test cases and playtest sign-off requirements.

Do I need GDDs and story files to automate QA plan generation?▼

Yes, GDDs and story files are needed to automate QA plan generation. The tool loads inputs from these files to extract acceptance criteria and implementation notes, which are required to classify test types and output a structured testing plan.

What is the best way to validate testing scope before coding begins?▼

The best way to validate testing scope before coding is to run automated QA plan generation. This reads your backlog and GDDs to classify stories by test type, outputting a structured plan with smoke-test scope and playtest notes to align the team.

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
wsmanwsman
18

qa-plan

Generates structured QA plans with story classifications and verification guidance.

Community
Advanced
FrancisVargaFrancisVarga

qa-plan

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

Community
Advanced