Work-product audit
Keep a repository readable as finished work rather than a transcript of how the work was produced.
Workflow
Identify the public surface: root docs, package documentation, docs/, examples, schemas, user-facing prompts, and CLI help. Exclude version-control data, caches, dependencies, generated output, internal notes, and agent scratch unless the request includes them.
Run the candidate scanner:
bin/work-product-audit <repo-or-file>
Review every hit in context. The scanner reports candidates, not verdicts.
Classify each item with references/decision-guide.md: delete, rewrite, move internal, or keep.
Edit with a deletion bias. Turn useful defensive or meta framing into a direct statement of behavior.
Re-run the scanner and the repository's link, style, or documentation checks.
Evidence rules
- Tie every recommendation to the audience and maintenance cost.
- Preserve operational boundaries that prevent concrete misuse.
- Distinguish an unsupported assurance from a claim backed by nearby evidence.
- Search for old names, task identifiers, local paths, session residue, and provider notes before publication.
- Treat patterns associated with generated prose as review cues, never proof of authorship.
Report
Group changes by delete, rewrite, move, and intentional keep. Explain any remaining candidate that could surprise a later auditor.
For an independent read-only pass, use agents/auditor.md.
1---2name: work-product-audit3description: Audit repositories and public documentation for internal notes, defensive explanations, unexplained assertions, stale project residue, hidden assumptions, and generated-sounding meta commentary. Use when scanning launch material, cleaning public prose, or deciding which reasoning belongs outside the finished deliverable.4---56# Work-product audit78Keep a repository readable as finished work rather than a transcript of how the work was produced.910## Workflow11121. Identify the public surface: root docs, package documentation, `docs/`, examples, schemas, user-facing prompts, and CLI help. Exclude version-control data, caches, dependencies, generated output, internal notes, and agent scratch unless the request includes them.132. Run the candidate scanner:1415 ```sh16 bin/work-product-audit <repo-or-file>17 ```18193. Review every hit in context. The scanner reports candidates, not verdicts.204. Classify each item with [`references/decision-guide.md`](references/decision-guide.md): delete, rewrite, move internal, or keep.215. Edit with a deletion bias. Turn useful defensive or meta framing into a direct statement of behavior.226. Re-run the scanner and the repository's link, style, or documentation checks.2324## Evidence rules2526- Tie every recommendation to the audience and maintenance cost.27- Preserve operational boundaries that prevent concrete misuse.28- Distinguish an unsupported assurance from a claim backed by nearby evidence.29- Search for old names, task identifiers, local paths, session residue, and provider notes before publication.30- Treat patterns associated with generated prose as review cues, never proof of authorship.3132## Report3334Group changes by delete, rewrite, move, and intentional keep. Explain any remaining candidate that could surprise a later auditor.3536For an independent read-only pass, use [`agents/auditor.md`](agents/auditor.md).
batteryshark