gaia-test-design

Assess project risks and generate a formal test plan using test-plan-template.md.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-test-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-test-design
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-test-design
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-test-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires resolve-config.sh, checkpoint.sh, lifecycle-event.sh, and includes scripts (resource) components.

What problem does it solve?

Designs and orchestrates risk-based test plans by coordinating with the test-architect subagent (Sable) to ensure comprehensive coverage across software projects.

Core Features & Use Cases

  • Collaborative risk assessment and test-strategy development with Sable.
  • Generation of formal test plans and artifacts documenting coverage and gates.
  • Guidance on test levels (unit, integration, E2E) and quality gates, with templates enforced.

Quick Start

Initiate a risk-based test planning session for your project by calling the gaia-test-design workflow and engaging the test-architect subagent.

Frequently Asked Questions about gaia-test-design

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

FAQPage Schema
How do I create a risk-based test plan for software projects?

A risk-based test plan identifies and assesses project risks, focusing on critical paths and data integrity. This Skill coordinates with the Sable test-architect subagent to design test strategy, map components to unit, integration, and E2E levels, and output a formal test plan.

How does the Sable test-architect subagent help with test strategy design?

The Sable test-architect subagent collaborates on risk assessment and test-strategy development. It maps software components to appropriate test levels and defines quality gates, ensuring the final test plan uses the bundled template and is written to docs/test-artifacts/test-plan.md.

What's the best way to map software components to unit, integration, and E2E test levels?

Mapping components to test levels requires assessing risk and coordinating test strategy. This Skill uses the Sable subagent to analyze critical paths and data integrity, then generates a formal test plan that documents coverage across unit, integration, and E2E levels with defined quality gates.

Can I use this workflow to generate test artifacts and quality gates for my project?

Yes, this workflow generates formal test artifacts and quality gates. It validates the test plan against the bundled test-plan-template.md and writes the final document to docs/test-artifacts/test-plan.md, ensuring comprehensive coverage and structured quality gates.

Do I need specific dependencies to run the gaia-test-design workflow?

The workflow relies on resolve-config.sh, checkpoint.sh, and lifecycle-event.sh scripts. These bundled scripts manage configuration resolution, checkpointing, and lifecycle events to ensure the test plan is properly validated and written to the designated artifact location.

Why should I use a risk assessment approach for software test planning?

A risk assessment approach targets critical paths and data integrity issues first. By coordinating with Sable to design the test strategy, you ensure comprehensive coverage that prioritizes high-risk areas and produces a validated formal test plan with clear quality gates.