gsd-add-tests

To generate unit and E2E tests from phase specs, you need a completed development phase with SUMMARY.md, CONTEXT.md, and VERIFICATION.md artifacts. The system analyzes these UAT criteria to produce a classified test plan and generates tests following RED-GREEN conventions.

The RED-GREEN workflow for test generation ensures tests are written to initially fail (RED) before implementation makes them pass (GREEN). This Skill generates tests following these conventions while preserving workflow gates for classification, plan approval, and verification-gap reporting.

Yes, you can use UAT criteria to create a classified test plan for approval. The system analyzes implementation details and classifies coverage into unit (TDD), E2E (browser), or Skip categories, producing a reviewable test plan before generating the actual test files.

Yes, the test generation process supports browser-level E2E checks. It applies to codebases where browser-based E2E checks are required, classifying these tests separately from unit tests to ensure comprehensive coverage of expected behavior.

The best way to prevent missed edge cases and regressions is turning a completed development phase into a clear, reviewable set of unit and browser-based E2E tests. This grounds the tests directly in the phase's UAT criteria and verification specs.

Yes, you need specific phase artifacts to run automated test generation. Your workspace must contain SUMMARY.md, CONTEXT.md, and VERIFICATION.md files, which serve as the single source of truth for defining expected behavior and determining what requires testing.