gsd-add-tests

Generate unit and E2E tests from UAT artifacts with RED-GREEN workflow.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-add-tests-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-add-tests
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-add-tests-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents regressions and reduces manual QA effort by turning a completed phase’s requirements into runnable unit and E2E tests that match UAT expectations.

Core Features & Use Cases

  • Phase-driven test generation: Uses SUMMARY.md, CONTEXT.md, and VERIFICATION.md for a consistent spec-to-test mapping.
  • TDD vs E2E classification: Classifies implementation touchpoints into unit tests, browser-based E2E tests, or skip cases.
  • RED-GREEN workflow with approvals: Preserves workflow gates including classification and test plan approval, RED-GREEN verification, and gap reporting.
  • Commit-ready output: Produces test files with a standardized commit message for the given phase number.

Quick Start

Ask it to generate tests for your completed phase by running the skill with the phase identifier, for example: "Generate tests for phase 3 using the UAT criteria from SUMMARY.md, CONTEXT.md, and VERIFICATION.md, and produce unit and E2E tests ready for RED-GREEN verification."

Frequently Asked Questions about gsd-add-tests

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

FAQPage Schema
How do I generate unit and e2e tests from UAT criteria?

You can generate unit and e2e tests from UAT criteria by reading SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications to map requirements into deterministic unit coverage and browser-based e2e validation.

How does red-green verification work for phase-driven test generation?

Red-green verification for test generation requires producing an approved test plan, writing tests that initially fail (RED), and modifying them to pass (GAP) while preserving workflow gates and classifications for the completed phase.

Can I use specification mapping to classify implementation touchpoints into unit tests and browser automation?

Yes, specification mapping classifies implementation touchpoints into deterministic unit tests, browser-based e2e tests, or skip cases based on the UAT criteria defined in your specification files.

What's the best way to structure commit-ready test files for a completed software phase?

The best way to structure commit-ready test files is to generate them with a standardized commit message that includes the phase number, ensuring the unit and e2e tests align with the phase's UAT expectations.

Do I need specific documentation files before starting phase-driven test generation?

Yes, you need SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specification inputs to map the phase requirements into runnable tests and reduce manual QA effort.

Why does test generation require an approved test plan before writing code?

Test generation requires an approved test plan to preserve workflow gates, ensuring the classification of unit tests, browser-based e2e tests, and skip cases is validated before red-green execution begins.