What problem does it solve? In an ML workspace, every experiment needs a paired pytest test, but deciding which test category applies and keeping file naming consistent across journal notes, experiment scripts, and test files is error-prone. This Skill acts as a router that enforces the pairing contract and dispatches test authoring to the right subskill. ## Core Features & Use Cases - Stem-pairing enforcement: Guarantees that tests/<category>/test_NN_<short_name>.py only exists when journal/NN_<short_name>.md is approved and experiments/NN_<short_name>.py exists, keeping the three artifacts 1:1. - Category dispatch table: Routes smoke, regression, and distribution test requests to the matching subskill (smoke-test-ml-pipeline in v1), defaulting to smoke when the request is ambiguous. - Scaffolding placement: Creates the empty pytest test file with a def test_*(): stub and TODO marker without overwriting existing files, then hands off assertion writing to the subskill. - Use Case: After a design note for experiment 02_feature_eng is approved, ask for its smoke test and the Skill verifies the journal and experiment files, places tests/smoke/test_02_feature_eng.py, and hands off to the smoke-test subskill. ## Quick Start Ask the assistant to write the smoke test for experiment 02 so it verifies the approved design note, scaffolds the paired pytest file, and dispatches to the smoke-test subskill.
