gsd-add-tests

Generate unit and E2E tests from UAT criteria with RED-GREEN verification.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-add-tests-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-add-tests
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-add-tests-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of unit and end-to-end tests from a completed project phase, accelerating validation and reducing manual testing effort.

Core Features & Use Cases

  • Test generation: Produces unit tests from implementation details and E2E tests for user flows based on UAT criteria.
  • Test planning: Generates a concise test plan and classifications (unit vs E2E vs skip) for quick approvals.
  • Automation-ready output: Commits tests with a standardized message to explicit version control practices.

Quick Start

Provide the phase identifier to start generating unit and E2E tests.

Frequently Asked Questions about gsd-add-tests

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

FAQPage Schema
How do I auto-generate unit and e2e tests from phase specs?

You can auto-generate unit and e2e tests by providing a completed phase identifier. The tool analyzes SUMMARY.md, CONTEXT.md, and VERIFICATION.md files alongside UAT criteria to classify tests, perform RED-GREEN verification, and commit changes automatically.

What is the RED-GREEN verification workflow for test generation?

The RED-GREEN verification workflow validates generated tests by first ensuring they fail without implementation (RED), then confirming they pass after code is applied (GREEN). This process ensures auto-generated unit and e2e tests accurately validate phase specifications and UAT criteria.

How do I classify tests into unit, e2e, or skip categories?

Tests are classified into unit, e2e, or skip categories by analyzing implementation files and user acceptance test criteria within a completed phase. The tool evaluates these inputs to generate a concise test plan that determines which tests to execute at each level.

Do I need SUMMARY.md and CONTEXT.md files to generate a test plan?

Yes, SUMMARY.md, CONTEXT.md, and VERIFICATION.md files are required inputs to generate a test plan. The tool parses these phase specification documents to extract implementation details and UAT criteria necessary for producing accurate unit and e2e tests.

What's the best way to automate test creation for user acceptance criteria?

Automating test creation for user acceptance criteria is best handled by generating e2e tests directly from UAT definitions. By analyzing phase documentation, the tool maps acceptance criteria to user flows, producing e2e tests and committing them with standardized messages.