gsd-add-tests

To generate unit and E2E tests from phase specifications, provide phase artifacts like SUMMARY.md, CONTEXT.md, and VERIFICATION.md to trigger an automated workflow that classifies tests and produces a test plan for approval.

The RED-GREEN test plan workflow analyzes your codebase to propose failing tests initially, then emits commit-ready test files with standardized messages to ensure implementation meets UAT criteria after the tests pass.

Test classification into unit, browser-based E2E, or skip categories happens automatically during the test plan generation phase, where the workflow analyzes your phase artifacts and codebase to present a categorized plan for user approval.

Yes, SUMMARY.md, CONTEXT.md, and VERIFICATION.md are required phase artifacts. The test generation workflow applies specifically to phases containing these files to ensure alignment with UAT criteria and implementation.

Yes, the workflow emits committed test files with standardized messages like 'test(phase-{N}): add unit and E2E tests from add-tests command' after you approve the generated test plan.

The best way to ensure implementation meets UAT criteria is generating unit and E2E tests directly from completed phase specifications, analyzing the codebase to produce a RED-GREEN test plan that validates implementation alignment.