derive-tests
Derive tests -- Turn Intent Into Tests
The docs say what the system should do. An audit finds where the code doesn't. Tests are what stop that gap from reopening after the next AI edit. This skill reads the documented intent, turns each load-bearing rule into a concrete test case, sorts them into what to automate, what needs a guarded live run, and what stays manual — then recommends the gate that keeps main honest: the one the repo's own instructions define, or a green-before-merge CI gate where they define none.
This produces a coverage map (tests.md) and concrete test cases, not a finished suite — you or the next agent implement the deterministic ones. If the repo already keeps a test-coverage file, under any name, that file is the map: update it rather than starting a second one (the shipping-artifacts skill's Locations and names rule).
Invocation
/ai-shipping:derive-tests Claude Code
/ai-shipping:derive-tests the checkout flow
$ai-shipping:derive-tests supabase/functions Codex
/ai-shipping:derive-tests check
"what should we test here" · "is our coverage map current" either agent, in plain words
A request that starts with check, or asks only whether the map is current, runs check-only mode (below) on the scope that follows it, instead of the workflow.