Review Spec

Assess a thread-root spec.md and every delta document under the thread's delta/ as a downstream handoff, strictly read-only. The one question you answer: could another agent plan and implement from this alone, without any hidden conversational context? You read them as that downstream agent would, judge them against the axes below, and record any findings for later attention. You never touch the spec, a delta document, 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 documents, as written, are fit for someone else to act on safely.

Inputs

Gather all of these before judging; the procedure below works from what you gather here.

• The project's AGENTS.md, when the file exists — the project's standing guidance for agents working in it.
• docs/glossary.md, when the file exists — the project's fixed terms, to be used in everything you write.
• docs/adr/ and docs/pdr/, read via /consult-decisions — the project decisions bearing on the change's subject.
• The roadmap entry named by the seed frontmatter's roadmap mapping, when the seed carries one — the entry this thread answers: its sketch, its scope boundary and its planned behavior, found as the heading whose text is roadmap.entry in the index at roadmap.path.
• The thread's spec.md — the reviewed target; it comes in that one form, at the thread root, in the shape <skill_path>/references/formats/spec.md defines. Read it end to end at least once, as a downstream planner with no memory of the conversation that produced it.
• The thread's delta/ — every delta document the thread holds, each read in full and against the shape <skill_path>/references/formats/delta-document.md defines, and each create under delta/docs/adr/ or delta/docs/pdr/ also against the shape <skill_path>/references/formats/decision-record.md defines, and each delta document targeting an agents file also against the shape <skill_path>/references/formats/agents-file.md defines. Read each edit and delete through the old/new rendering check-delta.mjs prints for it, rather than as escaped JSON strings. Inside the thread the delta takes precedence over the project records.
• The thread's log.md — the points the thread settled, the alternatives it rejected, and its document entries, which the record and coverage checks read the delta against.
• The thread's seed.md — why the thread exists.