test-design

Generate QA test plans from acceptance criteria for Unity features.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/igot-ai/os-twin --skill test-design-igot-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-design
Source: https://github.com/igot-ai/os-twin/tree/main/.agents/skills/roles/game-qa/test-design
Command: npx skills add https://github.com/igot-ai/os-twin --skill test-design-igot-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts story or feature specs into a complete test design workflow, bridging requirements to test artifacts and QA deliverables.

Core Features & Use Cases

  • Step 1 — Load Test Targets: locate relevant story or feature inputs (e.g., .output/design/gdd.md) and referenced project standards.
  • Step 2 — Categorize Tests: split into Unit, Integration, PlayMode, and Manual QA layers with clear criteria.
  • Step 3 — Write Test Cases: generate structured test case descriptions mapped to acceptance criteria.
  • Step 4 — Write Test Scaffolds: provide ready-to-copy test scaffolds for EditMode and PlayMode where needed.
  • Step 5 — Manual QA Checklist: produce a ready-to-use QA checklist for on-device validation and edge cases.
  • Step 6 — Save: output organized Markdown templates to .output/qa/test-plan-{feature}.md and guidance on next steps.

Quick Start

Input a story or feature spec and the skill will generate a complete test design workflow and Markdown templates.

Frequently Asked Questions about test-design

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

FAQPage Schema
How do I create a QA test plan from acceptance criteria for Unity?

Designing QA test plans for Unity features involves categorizing tests into Unit, Integration, PlayMode, and Manual layers. This skill bridges requirements to test artifacts by generating structured test cases mapped to acceptance criteria, ensuring comprehensive coverage for game development features.

How do I generate test cases and scaffolding code for Unity game development?

Generating test cases and scaffolding code for Unity involves mapping structured test case descriptions to acceptance criteria. The skill provides ready-to-copy test scaffolds for EditMode and PlayMode, along with a manual QA checklist for on-device validation and edge cases, outputting organized Markdown templates.

What is the best way to structure Unity test layers for a new feature spec?

The best way to structure Unity test layers is to split them into Unit, Integration, PlayMode, and Manual QA categories. This approach guides test case writing and scaffolding, ensuring both automated and manual validation paths are clearly defined for your game development feature.

Can I use a QA checklist to validate on-device edge cases for Unity PlayMode tests?

Yes, you can use a QA checklist to validate on-device edge cases for Unity PlayMode tests. The skill produces a ready-to-use manual QA checklist specifically designed for on-device validation, complementing the automated EditMode and PlayMode test scaffolds generated from your feature specs.

What input format do I need to generate Unity test design artifacts?

To generate Unity test design artifacts, you need to provide a story or feature spec, such as a game design document located at .output/design/gdd.md. The skill loads these relevant inputs and referenced project standards to produce a complete test design workflow and Markdown templates.