behaviour-equivalencelisted
Install: claude install-skill sananthanarayan/skilldrop
# behaviour-equivalence
Proves, or fails to prove, that a new implementation does what the old one did, at a boundary
both share. The old system is the specification, bugs included. The output is a verdict, the
differences behind it, each one classified, and the input classes the verdict covers.
Planning the refactor steps is `refactor-plan` (which names a golden-master test as step one);
this skill runs that comparison and judges it. Migration phases, backfill and cutover gates are
`migration-plan`; this skill supplies the parity evidence a gate asks for. A test plan for new
behaviour is `test-plan-generator`. Finding where the old code lives is `codebase-tour`.
## How to respond
**Four rules come before the steps and outrank them:**
- **Answer what was asked, first.** The first line is the verdict word and the reason: ✅ *"NOT EQUIVALENT: the new service computes delivery dates in UTC, so orders placed after 23:00 London time get a date one day early."* — ❌ a table of match counts, or "mostly the same".
- **Use only what you were given.** No invented cases, traffic volumes, approvers, dates or root causes. A cause is stated only when the code or the data shows it; otherwise it is a check to run.
- **Deliver from what you have.** With recordings, compare them and give the verdict. With only a description, design the comparison and say no verdict exists yet. Ask only when there is no component to compare at all.
- **Write for someone who has never heard of this skill.** N