Generates structured test plans and QA checklists for engine gameplay features.

Install

mkdir -p .claude/skills/qa-plan && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18150" && unzip -o skill.zip -d .claude/skills/qa-plan && rm skill.zip

Installs to .claude/skills/qa-plan

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Create a QA test plan for a system, feature, or milestone with test cases, smoke tests, and regression checks.
110 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Identify scope by reading GDD and stories
  • Define test categories like Smoke, Functional, Edge Cases
  • Create `test-plan.md` with structured test cases
  • Specify automated test class and method names
  • Outline Arrange/Act/Assert structure for automated tests
  • Review test plan for completeness and feasibility

How it works

The skill identifies the scope by reading design documents and source code, then defines test categories. It creates a structured `test-plan.md` and specifies automated test details.

Inputs & outputs

You give it
A system, feature, or milestone name
You get back
A `test-plan.md` file and test specifications for automated tests

When to use qa-plan

  • Create game feature test plans
  • Define QA checklists
  • Plan regression testing

About this skill

QA Plan Skill

Purpose

Create structured test plans that ensure quality through manual playtest checklists and automated test specifications for Flax Engine gameplay code.

Workflow

Step 1: Identify Scope

  • Read the target system GDD from design/gdd/systems/
  • Read implementation stories from production/stories/
  • Read the relevant source code from GameProject/Source/Game/
  • Identify all testable behaviors

Step 2: Define Test Categories

  1. Smoke Tests — Does it run? Basic functionality
  2. Functional Tests — Do features work as designed?
  3. Edge Cases — Boundary conditions, unusual inputs
  4. Integration Tests — Do systems interact correctly?
  5. Performance Tests — Within frame budget?
  6. Regression Tests — Did new changes break old things?

Step 3: Write Test Plan

Create tests/{system}/test-plan.md:

# Test Plan: {System Name}
**Version**: {date}
**Related Stories**: STORY-{NNN}, STORY-{NNN}

## Smoke Tests
| # | Test | Steps | Expected | Pass? |
|---|------|-------|----------|-------|
| S1 | {test name} | {how to test} | {expected result} | |

## Functional Tests
| # | Test | Precondition | Steps | Expected | Pass? |
|---|------|-------------|-------|----------|-------|

## Edge Cases
| # | Test | Condition | Expected | Pass? |
|---|------|-----------|----------|-------|

## Integration Tests
| # | Systems | Scenario | Expected | Pass? |
|---|---------|----------|----------|-------|

## Performance Tests
| # | Metric | Target | Measured | Pass? |
|---|--------|--------|----------|-------|

## Automated Tests
{List of C# unit tests to write}
- `{TestClass}.{TestMethod}` — {what it validates}

Step 4: Write Automated Test Specs

For each automated test, specify:

  • Test class and method name (following {System}_{Method}_{ExpectedResult} naming)
  • Arrange/Act/Assert structure
  • Flax-specific test setup (scene loading, actor spawning)

Step 5: Review

  • QA Lead reviews completeness
  • Developer reviews feasibility
  • Add to regression suite

Output

  • tests/{system}/test-plan.md
  • Test specs ready for implementation in tests/unit/ or tests/integration/

When not to use it

  • When the user wants to execute tests
  • When the user wants to write implementation code
  • When the user wants to perform deployment or documentation tasks

Limitations

  • The skill creates test plans, not executed tests
  • It focuses on manual playtest checklists and automated test specifications
  • It does not perform code implementation

How it compares

This skill generates a complete, structured QA test plan and automated test specifications, providing a systematic approach to quality assurance before testing begins.

Compared to similar skills

qa-plan side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
qa-plan (this skill)03moNo flagsIntermediate
qa-planning26moNo flagsIntermediate
criteria-generator04moNo flagsIntermediate
fmea-analysis05moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry