qa-test-design

Designs test strategies mapping acceptance criteria to unit, integration, and e2e scenarios.

3|Updated Feb 7, 2026

Search Tags:#qa #test strategy #acceptance criteria #quality gate #coverage #test design #test prioritization

Ready to run

npx skills add https://github.com/gabrielnsmnto/kord-aios --skill qa-test-design-gabrielnsmnto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-test-design
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/qa/qa-test-design
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill qa-test-design-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often write tests ad hoc, leading to redundant coverage at the wrong levels or critical acceptance criteria with no tests at all. This Skill turns a user story into a structured test strategy with clear level and priority assignments. ## Core Features & Use Cases - Test Level Assignment: Applies a unit/integration/e2e decision framework so each scenario is tested once at the right level. - Priority Classification: Assigns P0-P3 priorities based on business risk, revenue impact, and compliance needs. - Structured Outputs: Produces a test design document, a gate YAML block for quality gates, and trace references for requirement tracing. - Use Case: Given story 1.3 with five acceptance criteria, generate a test design matrix showing which ACs need unit tests, which need integration tests, and the recommended execution order starting with P0 tests. ## Quick Start Ask the QA agent to run test design for story 1.3 and produce the test design assessment with prioritized scenarios.

Frequently Asked Questions about qa-test-design

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

FAQPage Schema

How do I decide between unit, integration, and e2e tests for a story?▼

Use a test levels framework: unit tests for pure logic and calculations, integration tests for component interactions and database operations, and e2e tests only for critical user journeys and compliance paths. Prefer the lowest level that adequately covers the risk.

How do I prioritize test cases by business risk?▼

Classify scenarios into P0 through P3: P0 for revenue-critical, security, and compliance paths; P1 for core user journeys; P2 for secondary features; P3 for rarely used functionality. Execute P0 tests first for fast feedback.

What inputs does the test design workflow need?▼

It requires a story ID in epic.story format, the path to the story markdown file, and optionally the story title and slug, which can be derived from the story file if missing.

How do I avoid duplicate test coverage across levels?▼

Validate that every acceptance criterion has at least one test, no scenario is covered redundantly at multiple levels, and critical paths intentionally have multiple levels. A coverage checklist catches gaps before finalizing.

What outputs does a test design session produce?▼

It produces a test design markdown document saved to the QA assessments folder, a gate YAML block summarizing scenario counts by level and priority, and trace references for requirement tracing tasks.