auditlisted

# audit — whole-project assessment and purge `audit` inspects the **whole project** — never a single diff — and acts directly in this session. No copy-paste prompts, no external orchestrator: the skill dispatches its own subagent roles and delivers the result here. Two modes: - **assess** — an evidence-based health report across six dimensions (documentation, architecture, code quality, testing/reliability, security/config, product readiness), scored 1–10, harsh but fair. - **purge** — remove what is proven dead or false: dead code, misleading docs, stale branches, unused dependencies, old TODOs, architecture fiction. Every removal is evidence-backed, categorized for safety, and gated on human approval before anything risky happens. If the user's intent is ambiguous, ask which mode they want. "How healthy is this?" is assess; "get rid of what's dead/false" is purge. ## Do this 1. **Pick the mode** from the user's request (or ask). 2. **Create the scratch dir** — `mkdir -p .audit-notes/` at the repo root. It is gitignored process exhaust: never committed, regenerated per run. 3. **Dispatch the Mapper first (barrier)** — one subagent maps structure, toolchain, entry points, generated/vendor paths, and the branch inventory into `.audit-notes/00-map.md`. Nothing else starts until it exists. 4. **Dispatch the mode's roles** (briefs below and in `references/`), each reading the prior notes and writing its own file in `.audit-notes/`. 5. **Dispatch the Sy