Repo Audit

A leverage hunt, not a coverage exercise. This skill hunts the improvements that matter — deletions, leanness/performance wins, architectural deepening, missing capabilities — and synthesises them into an ordered roadmap of epics, fully reconciled against the repo's existing backlog.

When to use

• You want to know what the highest-leverage improvements in a repo are.
• The backlog has drifted from the codebase and needs a ground-truth reset.
• You're about to plan a significant quarter and want an ordered roadmap, not a flat pile of tickets.

When not to use

• You need just one domain: reach for staleness-audit, tdd, improve-codebase-architecture, etc. directly.
• The project is too early-stage to audit (no code yet, prototype only).
• You only need a quick PR review or a single-file fix.

Stage 1 — Context + backlog load