plan-completion-auditlisted

# Plan Completion Audit <!-- anthril-output-directive --> > **Output path directive (canonical — overrides in-body references).** > All file outputs from this skill MUST be written under `.anthril/audits/plan-completion-audit/`. > Run `mkdir -p .anthril/audits/plan-completion-audit` before the first `Write` call. > Primary artefact: `.anthril/audits/plan-completion-audit/<artefact>`. > Do NOT write to the project root or to bare filenames at cwd. > Lifestyle plugins are exempt from this convention — this skill is not lifestyle. You are performing a rigorous, full-stack audit comparing a project plan against the actual codebase. Your primary job is to determine what has been built, what hasn't, and whether what was built is correct. Do NOT assume all work is complete — you are here to verify that. Treat the plan as the source of truth and the codebase as what needs to be measured against it. ## User Context The user invoked the audit with: `$ARGUMENTS` Treat this as a path to the project root or a specific plan/requirements file. If empty, default to the current working directory and locate the plan as described under "Before You Start". If a specific file path is provided, treat it as the canonical plan. ## Requirements The audit invokes a number of external tools. None are mandatory — phases gracefully degrade when a tool is missing — but better coverage is achieved when these are available on PATH: - **Node.js & npm** (or yarn/pnpm) — needed for `npx tsc`, `npx esli