qa-plan

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

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill qa-plan-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/qa-plan
Command: npx skills add https://github.com/scomofo/dragon-forge --skill qa-plan-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA planning usually happens after implementation, which creates rework and missed regressions because the team only learns what to test once changes are already done.

Core Features & Use Cases

  • Sprint/feature/story scope resolution: Builds a plan from the current sprint, a specific feature/system, a single story path, or an entire epic.
  • Requirement-driven test classification: Reads story files and referenced GDD sections (Acceptance Criteria, Formulas, Edge Cases) to classify tests as Logic, Integration, Visual/Feel, UI, or Config/Data.
  • Actionable outputs for automation and hand-off: Produces automated-test requirements, manual verification steps, smoke test scope, and playtest sign-off rules, and writes the result to a dated file.

Quick Start

Run qa-plan for the current sprint so the team receives a structured QA plan covering automated tests, manual checks, smoke scope, and playtest requirements.

Frequently Asked Questions about qa-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a QA plan for Godot sprint scope from GDD acceptance criteria?

To create a Godot sprint QA plan, analyze story files and referenced GDD acceptance criteria to classify tests into Logic, Integration, Visual/Feel, UI, and Config/Data categories, producing a structured document with automated test paths and manual verification checklists.

What is requirement-based test classification for game features?

Requirement-based test classification reads GDD sections like Acceptance Criteria and Formulas to categorize tests into Logic, Integration, Visual/Feel, UI, or Config/Data, ensuring sprint scope coverage matches design specifications before implementation begins.

How do I plan smoke testing and playtest sign-off scope for a single story?

Plan smoke testing and playtest sign-off scope for a single story by resolving the story path, reading its GDD references, and generating a structured document specifying smoke test boundaries and required playtest sign-off evidence.

Does qa-plan work with missing GDD references in story files?

Yes, when missing story or GDD references are encountered, the QA planning process handles them conservatively, ensuring the generated test coverage document remains accurate without failing the sprint scope resolution.

How do I generate automated test paths and manual verification checklists for Godot systems?

Generate automated test paths and manual verification checklists by running requirement-driven QA planning on your sprint or feature scope, which outputs actionable test requirements and writes the results to a dated file for team hand-off.

Why should QA planning happen before implementation starts?

QA planning before implementation prevents rework and missed regressions by establishing test coverage, smoke test scope, and playtest sign-off rules early, so the team knows exactly what to test before changes are built.