qa-plan
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.zipInstalls 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.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
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
- Smoke Tests — Does it run? Basic functionality
- Functional Tests — Do features work as designed?
- Edge Cases — Boundary conditions, unusual inputs
- Integration Tests — Do systems interact correctly?
- Performance Tests — Within frame budget?
- 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/ortests/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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| qa-plan (this skill) | 0 | 3mo | No flags | Intermediate |
| qa-planning | 2 | 6mo | No flags | Intermediate |
| criteria-generator | 0 | 4mo | No flags | Intermediate |
| fmea-analysis | 0 | 5mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
qa-planning
WellApp-ai
Generate QA Contract with numbered Gherkin scenarios (G#N) and acceptance criteria (AC#N)
criteria-generator
openzigs
Converts ingested requirements into structured Given/When/Then acceptance criteria using RAG-powered LLM generation. Auto-tags criteria, assigns confidence scores, and maintains traceability links.
fmea-analysis
ddunnock
Conduct Failure Mode and Effects Analysis (FMEA) for systematic identification and risk assessment of potential failures in designs, processes, or systems. Supports DFMEA (Design), PFMEA (Process), and FMEA-MSR (Monitoring & System Response). Uses AIAG-VDA 7-step methodology with Action Priority (AP
tpp
photostructure
Work on a Technical Project Plan. Use when starting or continuing work on a TPP from _todo/.
acceptance-criteria
Eric-Pacheco95
You expand a user story into a complete set of acceptance criteria using Given-When-Then (Gherkin) format. Cover the happy path, edge cases, negative paths, and applicable non-functional criteria. The output is ready to paste into Jira or a BDD test harness.
lisa-acceptance-criteria
CodySwannGT
Acceptance criteria definition. Gherkin user flows (Given/When/Then), error states, UX concerns, and empirical verification from the user perspective.