gsd-add-tests

You generate unit and E2E tests by running the add-tests workflow on a completed phase, using its SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications. The workflow classifies the implementation and proposes a test plan for approval.

Test generation following RED-GREEN conventions creates deterministic tests based on your phase documentation. It automatically commits the generated tests with a standardized message format to ensure full traceability across your development workflow.

Yes, automated test generation classifies your completed phase implementation into unit tests, E2E browser tests, or skipped tests based on the phase content. It analyzes your documentation to determine the appropriate test type.

To generate tests from phase documentation, you need a completed phase with existing implementation and documentation, specifically SUMMARY.md, CONTEXT.md, and VERIFICATION.md files. The workflow uses these specifications to produce a test plan.

You should use automated test generation when a phase has existing implementation and documentation. It reads the phase specifications to create a test plan, applies RED-GREEN conventions, and commits tests with a required message format.

The add-tests workflow requires no external dependencies to run. It operates directly on your phase documentation files to classify work into unit and E2E tests, propose a test plan, and commit the generated tests.