Menu
Use first when the user asks for tests, correctness, high reliability, static reasoning, proof, or safety evidence.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
| name | verification-and-reliability |
| description | Use first when the user asks for tests, correctness, high reliability, static reasoning, proof, or safety evidence. |
Use first when the user asks for tests, correctness, high reliability, static reasoning, proof, or safety evidence. This is a router skill: use it to select the smallest relevant leaf skill, then read that leaf skill before doing the work.
Choose the proof style before changing code: test-first behavior discovery, specification-driven prevention, or sound approximation.
SKILL.md before implementing, reviewing, or advising.| Leaf Skill | Use When |
|---|---|
test-driven-development | Use when the next observable behavior can be captured by a failing test before implementation. |
cleanroom-software-engineering | Use when reliability risk requires precise specification, defect prevention, and small verifiable increments. |
abstract-interpretation | Use when many possible executions must be reasoned about with a sound over-approximation. |
design-by-contract | Use when reliability depends on explicit preconditions, postconditions, or invariants at a boundary. |
stepwise-refinement | Use when proof depends on preserving a high-level specification through implementation steps. |
Before loading a leaf, answer briefly:
Then load the chosen leaf skill and follow its workflow. Do not blend every nearby theory into the task; route narrowly and let evidence pull in more context only when needed.
Use when organizing a large local skill library into category router skills, refreshing a compact skill inventory, or deciding which leaf skill bodies need to be read before agent classification.
Use first for ambiguous failures, messy project context, surprising results, repeated failures, postmortems, or contested product and architecture framing.
Use first for API boundaries, module ownership, domain modeling, contracts, architecture seams, and recurring design structures.
Use first for bounded code edits, refactors, implementation, simplification, control-flow cleanup, or maintainer clarity before choosing a more specific theory skill.
Use to organize a large skill library into category routers, route new skills, and propose new categories when existing routers are insufficient.
Use first for work shaped by users, tools, procedures, runtime evidence, operational artifacts, interfaces, or organizational workflows.