qa-plan

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

Updated May 13, 2026

Search Tags:#acceptance criteria #gdd #qa planning #test case design #smoke testing #sprint workflow #playtest sign-off

Ready to run

npx skills add https://github.com/FrancisVarga/the-dream-machine --skill qa-plan-francisvarga

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill qa-plan-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA planning often happens too late, after implementation, which turns testing into a post-mortem instead of a proactive quality gate.

Core Features & Use Cases

Scope-driven QA planning: Generate a QA plan for a sprint, a feature, or a specific story by collecting the in-scope story files and their linked GDDs.
Test type classification: Classify each story into Logic, Integration, Visual/Feel, UI, or Config/Data based on declared Type: or inferred classification from acceptance criteria.
Actionable test artifacts: Produce a plan that specifies automated test file locations, manual verification steps, smoke test scope, and playtest sign-off requirements.

Quick Start

Run qa-plan with the argument sprint to generate a production-ready QA plan for the current sprint’s in-scope stories.

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 before implementation starts?▼

QA planning shifts left by reading story files and linked GDD acceptance criteria to classify tests into automated, manual, smoke, and playtest categories before implementation begins.

How do I structure sprint workflow test cases for smoke testing and manual verification?▼

Structure sprint test cases by classifying stories into Logic, Integration, Visual/Feel, UI, or Config/Data types, then outputting manual checklists, smoke test scope, and playtest sign-off paths.

What is scope-driven QA planning for a sprint or feature?▼

Scope-driven QA planning collects in-scope story files and their referenced GDD acceptance criteria to produce a complete test plan covering automated test requirements and manual verification steps for a sprint or feature.

Can I use GDD acceptance criteria to determine what to automate versus what to verify manually?▼

Yes, GDD acceptance criteria are read to classify each story and determine which requirements need automated test files, manual QA checklists, or playtest sign-off evidence paths.

Does test case design classification support both declared and inferred story types?▼

Test case design classification supports declared story types explicitly, and when undeclared, it infers classification into Logic, Integration, Visual/Feel, UI, or Config/Data from the acceptance criteria.