product-audit

# Product Audit The **CTO health check**: run every few features, before a release, or when the product is "done", to answer *"where do we actually stand, and what should we do next?"* across the entire product. **Recommend-only — it never fixes, opens issues, or edits the roadmap. It proposes; the human decides.** Its single write is its own persisted report: `docs/audits/<n>-<YYYY-MM-DD>.md`. ## 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`). This is the widest lens in the workflow. `review-change` audits a diff, `audit-pr` a PR, `audi...