skills.rest
lgwanai
lgwanaiCOMMUNITY
Explore all skills by this author →
GitHub

gsd-add-tests

Generate unit and E2E tests from SUMMARY, CONTEXT, and VERIFICATION specs.

4|1|Updated Mar 22, 2026
Search Tags:#tdd#unit testing#specification#e2e testing#red-green#generate tests#javascript browser
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-add-tests-lgwanai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-add-tests
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-add-tests-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents shipping untested features by generating reliable unit and browser-level E2E tests from a completed phase’s specs and implementation, aligned to UAT verification criteria.

Core Features & Use Cases

  • Spec-driven test generation: Uses SUMMARY.md, CONTEXT.md, and VERIFICATION.md as the source of truth for what must be tested.
  • TDD-style unit tests and E2E coverage: Classifies implementation into unit (TDD) vs browser E2E (or Skip) and then generates tests accordingly.
  • Gated quality workflow: Produces a test plan for approval, preserves required workflow gates, and verifies progress with RED-GREEN conventions.

Quick Start

Run the gsd-add-tests skill with your completed phase summary so it can generate unit tests and E2E tests that match the phase’s verification requirements.

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 software specifications?▼

To generate unit and E2E tests from specifications, use the completed phase's SUMMARY, CONTEXT, and VERIFICATION documents as input to automatically create tests aligned with UAT criteria.

What is spec-driven test generation and how does it work?▼

Spec-driven test generation uses your phase's SUMMARY, CONTEXT, and VERIFICATION specifications as the source of truth to classify implementation into unit or browser E2E tests and generate them deterministically.

Can I automatically classify implementation code into unit tests versus E2E tests?▼

Yes, implementation code can be deterministically classified into unit, browser E2E, or skip categories based on the phase's specifications and UAT verification criteria before generating the respective tests.

What's the best way to apply RED-GREEN test generation to completed implementation phases?▼

The best way to apply RED-GREEN test generation is by processing completed phase specs to produce a test plan, preserving approval and verification gates before committing the generated test files.

Why does test generation require approval and verification gates before committing files?▼

Approval and verification gates are required before committing test files to ensure the generated unit and E2E tests accurately satisfy the phase's UAT criteria and maintain strict RED-GREEN progress verification.

Related Skills

Explore More Software Engineering Skills→
zerAdazerAda

gsd-add-tests

Generate unit and end-to-end tests from UAT criteria and implementation files.

Community
Intermediate
jedmamostojedmamosto

gsd-add-tests

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

Community
Advanced
aslaiiaslaii

gsd-add-tests

Generate unit and E2E tests from phase documentation using RED-GREEN conventions.

Community
Advanced
onelee85onelee85

gsd-add-tests

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

Community
Advanced