plan-dead-code — Prove it is dead before anyone deletes it

Degree of freedom: MIXED. Tool config authoring and the baseline command set [LOW freedom — run exactly]; judging reachable vs proven-dead, and what must keep working, [HIGH freedom].

Plan-only. This pass deletes nothing — not a file, not an export, not a dependency, not a row. It produces plan-dead-code.md: a reviewed keep/kill list plus a ratchet baseline.

The failure mode this skill exists to prevent: an agent runs knip on a vibe-coded repo, gets 300 findings, and starts deleting. On a first run, most findings are misconfiguration, not dead code. Knip's own docs are explicit — running --fix "before your configuration is fully settled is dangerous", and ignore patterns are "a last resort" because "hiding a result is not the same as resolving it."

This skill vs neighbors