dev-testing

Unit test coverage enforcement validates that code changes meet minimum thresholds—typically 85%+—by running tests against acceptance criteria. This Skill enforces those thresholds at Gate 3 of your development cycle, generating a coverage report that maps tests to each acceptance criterion across Go, TypeScript, and Python implementations.

Yes. This Skill applies test-driven development (RED-GREEN-REFACTOR cycles) to guarantee every acceptance criterion has at least one corresponding unit test with sufficient coverage. It produces a Traceability Matrix that explicitly maps tests to acceptance criteria, making verification automated and transparent.

Unit test coverage validation supports Go, TypeScript, and Python implementations. You provide implementation files in your chosen language along with acceptance criteria and unit_id, and the Skill runs tests to generate a coverage report and Markdown-based Testing Summary.

The 85%+ threshold ensures critical paths and edge cases are tested, reducing the risk of undetected bugs reaching production. This requirement aligns with acceptance criteria verification, ensuring every feature requirement has corresponding test evidence before handoff to the next development gate.

This Skill generates a Traceability Matrix that explicitly connects each acceptance criterion to its corresponding unit tests and coverage metrics. The output includes a Testing Summary and Coverage Report in Markdown format, plus a Handoff document for downstream gates, making coverage gaps immediately visible.

Yes. This Skill runs at Gate 3 after Gate 0/1/2 handoffs, accepting unit_id, acceptance_criteria, implementation_files, and language as inputs. It validates coverage thresholds and produces a Handoff to Next Gate output, integrating seamlessly into automated development pipelines.