capture-consolidatelisted

# Capture Consolidate > "The requirements you want are in five different documents. > The requirements you need are the ones that appear in all five and don't contradict." > "A requirement stated twice is not two requirements. > A requirement stated twice differently is a problem." ## Core Philosophy Individual capture sessions — whether from transcripts or email threads — produce fragmented snapshots. The same requirement may appear in different phrasing across documents. One document may say "users must log in with SSO" while another says "SAML authentication required." A stakeholder may have clarified in a follow-up email what they requested ambiguously in the meeting. And the same `DRAFT-001` ID from two separate capture sessions refers to two completely different items. Consolidation makes the capture bundle coherent enough for spec generation. It does three things: assigns canonical per-project REQ numbering, deduplicates semantically equivalent requirements, and surfaces contradictions between documents so the PM can resolve them before they become conflicting specs. This is a PM-supervised process. The skill makes proposals; the PM decides. No requirement is dropped, merged, or renumbered without PM awareness. **What this skill does:** Reads all `DRAFT-NNN` capture documents, identifies duplicates and near-duplicates, surfaces contradictions, assigns canonical `REQ-XXX` IDs, produces a unified capture bundle. **What this skill does NOT do:** Write specs, resol