spec-capturelisted

# Spec: Capture ## Overview Capture extracts decisions from the current session and writes them into spec files. It never writes silently — it presents what it found, flags ambiguities, and asks for confirmation before touching any file. ## Protocol ### Step 1: Extract and group Read the session history. Group findings by capability area: - Explicit decisions: something the user stated or chose, with rationale present or inferable from context - Ambiguous items: looks like a decision, but intent is unclear — could be a preference, a temporary shortcut, or a decision that was never actually finalised - Implementation details that were never decided: things that emerged from code rather than from a choice (these do not belong in specs) ### Step 2: Present before writing Present findings to the user **before writing anything**: > "Here's what I extracted from this session, grouped by area. Confirm and I'll write — or correct anything that's wrong." > > **[Capability area]** > - Decision: [what was decided] — Rationale: [why] > - Decision: [what was decided] — Rationale: [why] > > **Flagged — intent unclear:** > - "[quote or paraphrase]" — Did you mean [interpretation A] or [interpretation B]? > > **Not capturing (implementation detail, no explicit decision):** > - [thing that emerged from code] — If this was a deliberate choice, tell me the rationale and I'll add it. Wait for confirmation before writing. ### Step 3: Write after confirmation Create or update capabilit