review-speclisted

# review-spec - find overlap and conflicts before they ship A spec or ADR is most useful when it's the **only** document making its claims. Two specs that cover the same feature area drift; two ADRs that contradict each other create silent ambiguity; a spec that ignores a relevant ADR ships behaviour that breaks an earlier decision. `review-spec` reads a target spec or ADR (the one being reviewed) and audits the existing corpus around it. It surfaces: - **Duplicates** - scenarios already covered in another `.feature` file. - **Overlaps** - the new doc and an existing doc cover related ground in ways that will drift over time. - **Conflicts** - the new doc contradicts an existing ADR or another spec. - **Missing cross-links** - relevant ADRs not referenced; relevant specs not referenced. - **Orphan decisions** - the new doc relies on assumptions that should themselves be ADRs. The skill is **read-only**. It writes nothing; it produces a report with file paths, line numbers, and quoted excerpts so the user can decide what to merge, split, or update. ## Phase 0 - Identify the target Resolve what's being reviewed. The skill accepts: - A path to a `.feature` file: `/review-spec specs/order-cancellation.feature` - A path to an ADR: `/review-spec docs/adr/0042-order-cancellation.md` - Nothing - review the most recently modified spec/ADR (`git log -1 --name-only`). - A PR context - review specs/ADRs added/modified in the current PR (`gh pr diff --name-only`). For each