gsd-add-tests

Generate unit and end-to-end tests from phase specifications and UAT criteria.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-add-tests-novatech2210-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/novatech2210-cmd/ImidusApp/tree/main/.codex/skills/gsd-add-tests
Command: npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-add-tests-novatech2210-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completing software phases often requires writing a large number of unit and end-to-end tests from phase specifications and UAT criteria. This Skill automates that work, reducing manual effort and ensuring test coverage aligns with acceptance criteria.

Core Features & Use Cases

  • Classifies implementation files into unit tests (TDD) or browser-based end-to-end tests based on the phase documentation and code context.
  • Generates a test plan and presents it for user approval, capturing decisions before test artifacts are produced.
  • Produces and commits test files following RED-GREEN conventions, reports gaps, and suggests remediation to reach green.

Quick Start

Run the add-tests command with a phase identifier to generate unit and E2E tests from the phase documentation.

Frequently Asked Questions about gsd-add-tests

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

FAQPage Schema
How do I automate unit and E2E test generation from phase specifications?

Automate test generation by running the add-tests command with a phase identifier to classify implementation files and produce unit or E2E test artifacts directly from phase documentation and UAT criteria.

What is the RED-GREEN convention for automated test generation?

RED-GREEN conventions structure test artifacts by initially failing to confirm test logic (RED), then reporting implementation gaps and suggesting remediation to achieve passing tests (GREEN).

How do I generate tests for a project phase defined by SUMMARY.md and CONTEXT.md files?

Generate tests by targeting a completed phase that contains SUMMARY.md, CONTEXT.md, and VERIFICATION.md documentation, which the tool uses to classify and build the corresponding test files.

Does this automated test generation tool classify files into unit tests and E2E tests automatically?

Yes, the tool automatically classifies implementation files into unit tests following TDD principles or browser-based end-to-end tests based on the phase documentation and code context.

Can I review the test plan before the tool generates the actual test files?

Yes, the tool generates a test plan and presents it for user approval, capturing your decisions before any test artifacts are produced and committed with a standardized message.

What are the limitations of automating test generation from UAT criteria?

This automation requires a completed phase defined by specific documentation files and surfaces implementation gaps for manual remediation, meaning it does not automatically fix the underlying code to reach green.