ai-tells-reviewlisted

# AI Tells — Structural Review A judgment-based pass that catches the subtle tells the surface scan misses. Cite each finding, name the family, suggest a fix-direction. Then offer to rewrite. ## When To Use - Public-facing artifacts: READMEs, shipped docs, blog posts, release notes - Technical writing where the prose itself is the deliverable - After `ai-tells-scan` has already stripped the obvious tokens - When a draft "reads AI" but you can't articulate why - Before publishing anything Nick wouldn't want attributed to a machine Skip when: the artifact is internal-only and nobody cares, or the user only wants the mechanical pass (`ai-tells-scan` is enough). ## Workflow 1. **Read the artifact end to end.** Don't pattern-match line by line yet. Get the rhythm and shape first. 2. **Run the four-family rubric** below. For each tell found, note: line(s), family, why it reads as a tell, fix-direction. 3. **Produce the findings report** in the structure under "Output Shape." 4. **Offer the rewrite** explicitly: "Want me to do a pass that fixes these?" 5. **If yes, rewrite preserving structure and content.** Don't change what the doc is saying — change how it's saying it. The user can stop at the report. Don't rewrite without explicit consent. ## The Four-Family Rubric ### 1. Structural Reflexes Default shapes the model reaches for regardless of fit. - **Aphoristic closer.** Sentence trying to land like a punchline at the end of a section. Examples: "Premature alerts prod