gsd-add-tests

Generate unit and E2E tests from phase documentation with RED-GREEN workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates and validates test plans for a software phase by transforming phase documentation into executable tests, reducing manual effort and ensuring alignment with UAT-like criteria.

Core Features & Use Cases

  • Parse SUMMARY.md, CONTEXT.md, and VERIFICATION.md to define test scope and acceptance criteria
  • Classify implementation files into TDD (unit), E2E (browser), or Skip, and generate a test plan for user approval
  • Generate tests following RED-GREEN conventions and commit them with the specified message while preserving workflow gates

Quick Start

Run the add-tests workflow with the phase identifier to generate and commit 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 documentation?▼

You can auto-generate unit and e2e tests by parsing SUMMARY.md, CONTEXT.md, and VERIFICATION.md to define test scope, then classifying implementation files into TDD or E2E categories to produce a test plan.

What is the RED-GREEN test generation workflow for software phases?▼

RED-GREEN test generation creates executable tests from phase documentation, validates them against acceptance criteria, and commits the test files while preserving classification and test plan approval gates.

How do I classify implementation files for unit testing versus browser testing?▼

Implementation files are analyzed and classified into TDD for unit tests, E2E for browser tests, or Skip, based on the scope and acceptance criteria defined in the phase documentation.

Do I need specific markdown files to generate a test plan?▼

Yes, you need SUMMARY.md, CONTEXT.md, and VERIFICATION.md files to define the test scope and acceptance criteria required to automate the creation of unit and end-to-end tests.

How are generated tests committed in automated test generation workflows?▼

Generated tests are committed using the message test(phase-{N}): add unit and E2E tests from add-tests command, ensuring all workflow gates and gap reporting are preserved.

Can I review the test plan before tests are generated?▼

Yes, the workflow presents a test plan for user approval after classifying implementation files, ensuring you can review the proposed unit and e2e tests before generation and commitment.