review-speclisted

# Review Spec Assess a thread-root `spec.md` as a downstream handoff, strictly read-only. The one question you answer: **could another agent plan and implement from this spec alone, without any hidden conversational context?** You read the spec as that downstream agent would, judge it against the axes below, and record any findings for later attention. You never touch the spec or any other artifact, and you produce no durable report — a clean spec earns a chat judgment and nothing on disk. This is a quality-of-handoff and planning-readiness review; your concern is whether the document, as written, is fit for someone else to act on safely. ## Procedure 1. **Resolve the thread.** Work inside one thread root at `docs/threads/<YYMMDDHHMMSSZ-slug>/`. If `cwd` already sits inside a thread root, that is the thread. Two situations make a findings bundle physically impossible — `.pending-reviews/` would live inside the very thread that failed to resolve — so in both, refuse in chat, write nothing, and end with `Outcome: REFUSED — <reason>`: no thread exists yet, or several thread roots exist and which is active is ambiguous (never silently pick the most recent stamp). 2. **Read the spec read-only.** The target is the thread-root `spec.md`. Read it end to end at least once, as a downstream planner with no memory of the conversation that produced it. If no `spec.md` exists at the thread root, tell the user there is nothing to review, write nothing, and end with `Outcome: REFUSED —