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. ## Inputs Gather all of these before judging; the procedure below works from what you gather here. - `docs/adr/`, read via `/consult-adrs` — the project decisions bearing on the spec's subject. - `docs/glossary.md`, read via `/consult-glossary` — the project's fixed terms, to be used in everything you write. - The thread's `spec.md` — the reviewed target, and the review's only target; it comes in that one form, at the thread root. Read it end to end at least once, as a downstream planner with no memory of the conversation that produced it. - The thread's `seed.md` — why the thread exists. - The thread's `adr/` and `glossary.md` — the thread's delta of the project layer and the constraint sources a spec must not contradict; inside the thread they take precedence over the project records. ## Procedure 1. **Gather the inputs.** Read ever