inspectlisted

# Inspect Audit the **named targets**, label what you find by severity, and produce one plan doc. **Write no code.** **Use when:** two components look like they overlap; a file has grown and nobody knows what is still reachable; a component's logic needs checking before you build on it. **NOT for:** reviewing a diff (`/code-review`), shrinking one file's prose (`/trim`), or breaking an already-understood spec into tasks (`/plan` — go straight there). State the targets and their line counts in one line so the user can interrupt. ## Scope The named paths, nothing else. No target → ask which files; never guess. Reading is unrestricted — read anything, anywhere, to *prove* a finding. **Editing is zero.** `/inspect` never modifies a file, including its targets. The deliverable is a document, and the user decides whether any of it gets built. One exception: a `build-<slug>.md` plan the refact plan supersedes is deleted in the same pass — §Superseding a build plan. ## Step 0: Required reading (blocking) 1. `references/SKILL.md` — route to the docs covering the targets' feature area 2. `references/development/conventions.md` — Rules 1–9; half the detections below are restatements of them 3. Whatever feature/data doc SKILL.md routes to for each target A finding that contradicts a reference doc is a finding **about the doc too**. Record both; the doc is as likely to be wrong as the code. > **No `references/SKILL.md`?** The reference layer isn't set up here — skip Step 0 an