gsd-add-tests

You generate unit and e2e tests by running a workflow that reads phase documentation like SUMMARY.md, CONTEXT.md, and VERIFICATION.md to analyze implementation files, propose a test plan, and commit automated test code.

The RED-GREEN convention for test generation dictates writing tests that initially fail against UAT criteria, then refining them to pass, ensuring the final committed test code validates the implementation correctly.

Implementation files are classified into unit, e2e, or skip categories during test planning by analyzing the phase's UAT criteria and documentation, which then presents a proposed test plan for user approval before code generation.

Yes, automating phase test creation requires SUMMARY.md, CONTEXT.md, and VERIFICATION.md files, which provide the UAT criteria and implementation details required to generate valid unit and e2e tests.

When automating test generation from UAT criteria, generated tests are committed using a standardized message format like test(phase-{N}): add unit and e2e tests, directly integrating the new test code into your repository.