product-auditlisted

# Product Audit Product-wide health check. It only writes `docs/audits/<n>-<YYYY-MM-DD>.md`; every proposed action remains a user decision. ## Turn contract — verify before ending the turn ``` ✓ The full PRODUCT AUDIT report was printed in the fixed output format (health by dimension, F-numbered ranked findings, four proposal streams — the roadmap streams always present, `none — <why>` when empty) ✓ The report was WRITTEN to `docs/audits/<n>-<YYYY-MM-DD>.md` (incremental audit id) and committed — the file is the durable deliverable, the chat print is a copy ✓ Nothing else was fixed, filed, or changed — the report file is the ONLY mutation ✓ The closing `→ Next:` block is printed as the ABSOLUTE last output ``` About to end the turn with any box unchecked? The turn is NOT done — complete the missing box first (weak models drop end-of-document duties; this list is first on purpose). ## When to use - Periodically (every few features) or at a product-ready milestone. - When you want the broad, honest picture — quality, security, debt, docs, and roadmap — not the review of a single change (`review-change`) or PR (`audit-pr`). Unlike diff, PR, or docs-only reviews, this skill covers the whole product. ## Scope The entire codebase and its process artifacts: source, tests, the docs tree, the roadmap, the fix index, open issues, and every feature folder's planning docs. Accept an optional path/area to focus a partial audit; state the scope and, if you sample rather than exh