- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add phuryn/product-engineering --skill derive-tests -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add phuryn/product-engineering --skill derive-tests -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add phuryn/product-engineering --skill derive-tests -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add phuryn/product-engineering --skill derive-tests -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/phuryn/product-engineering/tree/HEAD/ai-shipping/skills/derive-testsDe l'éditeur
Turn documented intent into test cases that keep gaps from reopening. The docs say what the system should do; an audit finds where the code doesn't. Read that intent and turn each load-bearing rule into a concrete case. Sort cases into automated tests, guarded live runs, and manual checks. Recommend the repo's defined gate, or green-before-merge CI where it defines none.
Produce a coverage map and concrete cases, not a finished suite. You or the next agent implement the deterministic cases. If the repo already keeps a test-coverage file, under any name, update that map instead of starting another. Apply the shipping-artifacts skill's Locations and names rule.
Use check-only mode for a leading check or a map-currency question. A request starting with check, or asking only whether the map is current, checks the scope that follows instead of running the workflow.
/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
Write down intent before deriving tests from it. If system docs are missing or thin, apply the document-app skill first. Use the repo's docs location, or documentation/ by default. This skill reads flows.md, permissions.md, and automation.md most heavily. Where intent is absent, say so rather than inventing rules to test.
Read the applicable system docs, treating their claims as unverified. Read architecture, flows, permissions, variables, and any emails, cron, seo, and automation docs that exist. Apply the shipping-artifacts skill for each document's contents. Apply the intended-vs-implemented skill for the discipline of treating docs as claims to verify, not proof.
Inventory existing assertions before claiming any rule is covered. Read the test files, what they actually assert, and what runs in CI today. Distinguish coverage that exists now from coverage you propose; otherwise, the map can claim rules are pinned when nothing checks them. If there are no tests, say so plainly: that is itself a finding.
Extract deterministic rules whose violation crosses a consequential boundary. These are the load-bearing trust, data, money, tenant, or privacy rules:
flows.md and the matrix in permissions.md;automation.md.Skip cosmetic behavior; test rules whose failure harms someone other than the actor.
Mark coverage existing only when a repository test asserts the rule today. Build one row per use case:
rule → expected behavior (including the negative case) → evidence source (doc + code) → test type → status (existing / proposed / none).
Use these test types:
Separate a test's dependencies from whether the repo makes it gate. The repo's gate policy decides the latter (Step 5). A product may gate against its development database and identity provider's development instance, with real browser sessions, as in the test-harness skill. Those rows are deterministic there because the product owns the environments.
Map each flows-doc journey to the end-to-end spec that exercises it. Read the spec's assertions and identity setup; a filename alone proves no coverage. Flag a journey whose only tests fake identity or the browser, even when those tests prove its data rules. Record missing specs and any paid or real-inbox steps left to live or operator suites; the gate covers surrounding steps.
Default to deterministic unit, integration and applicable end-to-end suites without a stated gate. These tests pass or fail the same way on every run; guarded-live and manual rows don't gate. The owner decides a smaller set, recorded where the repo keeps its decisions, with its reason and revisit trigger. Prefer unit tests where decision logic can be isolated. Use integration when the rule lives in middleware, RLS, or auth-guard wiring that only a real dependency can exercise, and end-to-end tests for user journeys.
A pure helper complements testing real enforcement; it never replaces it. When a rule can only be exercised live, you can extract its decision into a pure, unit-testable helper. That proves the helper's logic, not that the framework calls it. Wiring and policy enforcement still need an integration or guarded-live check: route middleware, DB row-level security, auth guards, and provider config. Otherwise, the helper can pass while the real path is unprotected.
Write a concrete case for every rule a deterministic test can pin. For each unit, integration or end-to-end case, give its name, arrange/act/assert intent, and negative case it must reject. Group cases by the doc or flow they defend. Prefer the smallest test that pins the rule: one clear assertion per boundary, rather than an integration test that fails for ten reasons.
Follow the repo's stated gate policy instead of proposing a replacement. Start from its agent instructions, contributing guide, or release docs. They may define a local command plus human go, hosted CI, or another merge or release gate. Record that policy and its source in the coverage map, and check the deterministic set runs inside it. Don't recommend hosted CI or branch protection over the stated policy. If that gate omits the deterministic set, report a finding for the owner rather than proposing a different gate.
Where no policy exists, suggest CI matched to the repo's tooling. Recommend it; don't silently install it. Match the repo's stack and existing tooling:
main on green via a required status check plus branch protection.Output the workflow file and branch-protection setting as a clearly labeled suggestion for user approval, not an applied change.
Keep existing coverage, proposed tests, and unverified gaps in separate sections. Write tests.md with:
The gaps are the backlog, where the next AI edit can silently break a boundary. Proposed coverage is not existing coverage: a rule isn't covered until a test actually asserts it.
Check the map without rewriting it or running the tests. This lets a release check a map maintained by hand or by whoever runs the gate. Write no file: neither the map nor a report. Read the tests; don't run them. Don't apply the document-app skill when docs are thin; list them under Not checked.
shipping-artifacts skill's Locations and names rule, as the workflow does. If absent, put map comparisons under Not checked; still list flows-doc journeys missing end-to-end specs.Print the output in the conversation:
Coverage check: [scope] — check-only, no files written
### Stale entries
1. [rule or row]
- Map says: [entry] — `[map path]:[line]`
- Docs or tests say: [what they state or assert] — `[path]:[line]`
- Owner decides: fix the map, the doc, or the test.
### Not checked
- [thin or absent docs, tests whose assertion couldn't be read, areas out of scope]
### Journeys without end-to-end coverage
- [flows-doc journey and line → missing spec or identity/browser fakes; any live/operator step]
### Summary
Coverage check, [date], commit [short SHA], scope [scope]: [N] map rows read, [N] stale entries, [N] not checked. Tests read, not run. No files written. Which side to fix is the owner's call.
State what was read when the Stale entries section is empty. Then stop: don't offer to rewrite the map.
Write the map and full report to the repo's existing locations. Use the defaults below only where it has none, giving the user both paths and saying which are plugin defaults:
documentation/tests.md;reports/test_plan_{timestamp}.md.Test Coverage: [scope]
| Use case | Rule (doc) | Expected behavior (+ deny case) | Evidence | Type | Status |
|----------|-----------|---------------------------------|----------|------|--------|
[status: existing / proposed / none]
### Existing coverage
[tests already in the repo, each tied to the rule it pins]
### Proposed tests
[grouped by flow/doc — name · assert · negative case · type]
### Journeys
[flows-doc journey → end-to-end spec and case → real-session coverage → missing or live/operator steps]
### Gate
[the repo's stated gate policy, with its source, and whether the deterministic set runs inside it — or, where it states none, a workflow snippet for the detected stack + "green-before-merge" branch-protection note]
### Gaps — documented but unverified
[rules with no test yet, ranked by what crossing them exposes]
document-app skill.security-audit-static skill for the gap audit itself. For the full document → audit → test → packet sequence, use the ship check (/ai-shipping:ship-check, or $ai-shipping:ship-check in Codex).Each rule's origin, the case that taught it, is in receipts.md beside this file; read it when a rule's edge is unclear.
Every documented rule has a row, every row marked existing names a test that asserts it today, and the gaps are ranked. Every journey names its end-to-end spec or gap; in check mode, nothing on disk changed.
'What should we test' or a coverage map: derive the coverage map and missing tests from docs and code; check mode reports staleness.
---name: derive-testsdescription: 'What should we test' or a coverage map: derive the coverage map and missing tests from docs and code; check…---# ai-shipping/skills/derive-tests/SKILL.mdFAQ
Téléchargez ai-shipping/skills/derive-tests/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/phuryn/product-engineering.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.