project-auditlisted

Use when someone asks what is actually true of a whole project right now — what is finished, what is half-built, what is broken, and what nobody has looked at. Walks a cold start: discover what the project is, run a registry of probes chosen from that, read production evidence (published artefact against source, CI history, telemetry present or absent), then leave a self-contained HTML report and a JSON sidecar so the next audit can say what moved. Read-only: it proposes board rows and commits nothing. Triggers - 'project audit', 'audit the project', 'codebase audit', 'state of the project', 'what is unfinished', 'project health check', 'аудит проекта', 'проаудируй проект', 'состояние проекта', 'что не доделано', 'аудит кодовой базы'. Not for: auditing one deliverable inside a run (that is the pipeline's own ladder), reviewing a diff, or checking a skill's construction — say 'без диагностики' to opt out.
ssheleg/task-pipeline · ★ 4 · Code & Development · score 77

Install: claude install-skill ssheleg/task-pipeline

# Project audit — what is true of this project right now **A gate asks whether an artifact is good. Acceptance asks whether anything on the list was lost. Neither asks what the project actually is today**, and that is the only question an operator has when they open a repository they have not touched for a month. This skill answers it from a cold start — no brief, no REQ table, no module map required — and leaves two artefacts: a page a person reads, and a sidecar the next audit reads. ## Contents - What this is not - The six phases - Three verdicts, and why the third one exists - The class that version checks cannot see - The two artefacts - What the script does and what you do - Exit criterion - Rationalizations ## What this is not | | Owns | Reach for it when | |---|---|---| | [`references/audit.md`](../task-pipeline/references/audit.md) | the **method** — the L0→L7 ladder, seams, axis rotation | one deliverable is being walked inside a run | | this skill | the **procedure** — cold start, probes, production, the report | a whole project is the subject | | `/skill-audit` (make-skill) | a skill's construction against the standard | the thing audited is a skill or plugin | | `/ux-audit` (super-ux) | code against documented scenarios | the question is user-facing behaviour | | `/seo-aeo-audit` (seo-aeo-audit) | a public surface's search and answer-engine visibility | the question is whether a machine will find it | **The method is not restated here.** Phase 4 below hand