qa-plan

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

72|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill qa-plan-striderza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/qa-plan
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill qa-plan-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of teams lacking a clear, upfront QA roadmap for a sprint or feature, causing missed edge cases and late rework.

Core Features & Use Cases

  • Scope-driven QA planning: Builds a QA plan from a sprint, feature, story, or epic scope by discovering in-scope story files.
  • Story test-type classification: Classifies each story by test type (Logic, Integration, Visual/Feel, UI, Config/Data) based on story headers and acceptance criteria.
  • GDD-aware test allocation: Reads referenced GDDs and uses the GDD Acceptance Criteria and Formulas to determine what must be automated vs verified manually.
  • Operational outputs for the team: Produces automated test requirements, manual QA checklists, smoke test scope, and playtest sign-off requirements, and specifies the output location for the generated plan.

Quick Start

Run qa-plan for the current sprint to generate a structured QA plan at production/qa/qa-plan-[sprint-slug]-[date].md.

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 from story files and acceptance criteria?

To generate a sprint-ready QA test plan, the Skill reads in-scope story files and referenced GDD acceptance criteria, then outputs structured test plans with automated test paths, manual checklists, and smoke test scope.

What is the best way to classify tests by type for logic, integration, and UI stories?

Classifying tests by type involves reading story headers and acceptance criteria to allocate tests into logic, integration, visual/feel, UI, or config/data categories, ensuring automated paths and manual verification are correctly separated.

How does GDD-aware test allocation work when planning QA for a sprint?

GDD-aware test allocation works by reading referenced Game Design Documents to extract acceptance criteria and formulas, using them to determine exactly which test requirements must be automated versus manually verified.

Can I use this for pre-sprint QA planning or does it only support pre-implementation?

You can use this for both pre-sprint and pre-implementation QA planning. It applies to any stage where tests must be allocated by story type and requires playtest sign-off before development concludes.

What outputs are included in a structured QA test plan for sprint workflows?

A structured QA test plan includes test summary tables, required automated test paths, manual verification checklists, smoke test scope, and playtest sign-off requirements, saved directly to your production directory.

Do I need specific dependencies to generate sprint test plans and playtest sign-off requirements?

No specific dependencies are required. The Skill operates independently to read story files and GDD formulas, generating a complete QA plan with smoke test scope and sign-off requirements without external tools.