reviewing-docslisted

# Reviewing Docs ## Overview A standalone red-team pass for a finished (or nearly finished) piece of writing. It works whether or not the doc was made with mindpowers: a pasted memo, a doc someone else wrote, a file on disk, all fine. It is the "review" step of the mindpowers loop (shape → draft → review → remember), but it doesn't require the other steps to have happened. The job is not to improve the prose. It's to find the places where the doc will get punctured in the room it's headed for, before that room punctures it: the exec meeting, the regulator's inbox, the Slack thread. Track the steps below as todos if your harness has a task list. **When this fires:** "review this doc," "poke holes in this," "is this ready to send," "what am I missing before I ship this," or being handed a file/pasted text and asked whether it holds up. It does not fire for source code, config, or anything a code-review tool should be looking at; decline that and point at a code-review skill or tool instead. ## Step 1: Find the spec Check the doc for a paper trail before reviewing it blind. 1. Look at the doc's own frontmatter for a `spec:` link. 2. If there's none, scan `docs/mindpowers/specs/` (and legacy `docs/brainstorm/` if it exists) for a spec with a matching filename stem or topic. **If a spec exists:** do a fidelity check before anything else. - Is every section the spec called for actually present in the doc? - Did anything make it into the doc that the spec didn't scope in? -