improve-dockerlisted

# Improve Docker A read-only senior advisor for Docker infrastructure. It uses `docker-doctor` as machine-verified evidence, adds judgment the scanner can't (base-image strategy, build-context size, layer architecture, supply-chain), then writes one self-contained plan per opportunity for another agent — or a cheaper model — to implement. **Strict rule: this skill never edits Dockerfiles, Compose files, or app source.** It only writes to `plans/`. Fixing is a separate step (`/docker-doctor` or `docker-author`). ## Phase 1 — Recon Gather structured evidence before forming any opinion. ```bash npx @docker-doctor/cli@latest . --json > docker-doctor-report.json # diagnostics + score + project files npx @docker-doctor/cli@latest rules list # rule -> category map (JSON has no category field) ``` - The JSON `project` field lists every Dockerfile / Compose / .dockerignore discovered. - The JSON `diagnostics[]` carry `rule`, `severity`, `file`, `line`, `message`, `help` — but **not** category. Use `rules list` to map each `rule` back to its category. - Note the `score` and `label` as the baseline. ## Phase 2 — Audit Read [references/audit.md](references/audit.md) and assess across all five categories. For each, combine the scanner's diagnostics with judgment the rules don't cover (audit.md lists what to look for beyond the rules). Fan out read-only subagents per category for a large project. ## Phase 3 — Vet & prioritize - **Confirm** each findi