Review Lossless Mapping

Read a document and the discussions it was produced from, READ-ONLY, and emit a references-first review report into the reviewed document's reviews/ folder. This skill verifies that the document is a lossless and additive-free mapping of what the user actually saw and accepted in the discussions: nothing the user never agreed to was smuggled in, and nothing the user decided was dropped. It does not edit the document, it does not ask clarifying questions one-at-a-time, and it does not walk findings with the user. It does not commit.

This is the detection side of the document's own authoring constraint: a document (typically a spec) is supposed to commit to no decision or assumption the user did not see and accept in the discussions, unless the document explicitly marks it a Degree of Freedom. This review confirms that obligation was met. This skill produces the findings; a separate discussion disposes them.

Inputs

This skill accepts two kinds of input:

1. The document under review — the artifact produced from the discussions. Typically a spec at specs/NNN[-<desc>]/spec.md inside the thread root, but it may be ANY document produced from discussions (a proposal, a plan, or another artifact). The path may be passed thread-relative or repo-relative.
2. The discussions (and/or upstream input) the document maps from — the source decisions the document is supposed to faithfully carry. These are typically the thread's discussion and decision-log records under the document's discussions/ folder (or seed/discussions/ for genesis discussions, or an upstream proposal's discussions/).

If the document path is not supplied, ASK the user which document to review — do not pick by recency. If the thread holds multiple lineages of the same type (specs/001-api/, specs/002-cli/) and the user's reference is vague ("the spec"), ASK which lineage is intended. There is NO "most recent lineage" or "highest NNN" fallback — silently picking by number would hide a real decision (which lineage the user means) behind a sort order. If the reference could point at a document in another thread, ASK which thread.

If the discussions are not explicitly named, locate them under the document's discussions/ folder and the thread's genesis discussions, and confirm the resolved set with the user before reading. Mapping against the wrong set of discussions invalidates the whole review.

What "Lossless and Additive-Free" Means