specify-baseline-tests

You can create regression tests for uncovered code coverage gaps by reading blast-radius.yaml to map gaps to code symbols and generate a structured baseline-tests.yaml specifying current observable input/output behavior and assertions.

A baseline test specification documents a system's current observable behavior before changes are made. You need one when existing tests do not cover specific functions, class methods, or module-level side effects and you need regression safety.

You generate YAML test specifications for TDD workflows by analyzing current entry point behavior from coverage gaps and producing a ready-to-implement baseline-tests.yaml file that includes framework selection, assertions, and suggested test file locations.

Yes, you can pin current code behavior by generating a specification that documents what the system currently does rather than prescribing new behavior, writing only the structured baseline-tests.yaml output without implementing the actual test logic.

The specify-baseline-tests skill writes only the specification output. It produces a structured baseline-tests.yaml including input/output behavior, assertions, framework selection, and suggested test file locations for downstream teams or tools to implement.

The limitation of generating baseline regression tests is that the output is restricted to a specification file. It does not generate actual executable test code, requiring downstream tools like test-engineer to implement the tests from the baseline-tests.yaml.