specflow-ingestlisted

# Specflow: Document Ingest ## When to use Read external documents (client briefs, meeting notes, requirements updates, stakeholder emails, technical specs, product docs, or any free-form input) and reconcile them against the existing spec trees to produce a structured change manifest. Uses parallel agent plans, section-based processing with delegation for large documents, internal conflict detection, and temporal/version awareness. This skill proposes changes — it does not execute them. Approved changes are routed through the change-router for execution. Trigger on: "here are the new requirements", "update specs from this", "the client sent this", "ingest this", "reconcile this with specs", "what changed from this brief", or any document drop in a Specflow-managed project. ## What this skill does Turn external documents into structured spec change proposals. This skill is the intake layer — it reads what humans and clients produce and translates them into the language of the spec tree. **This skill proposes. It does not execute.** The output is a change manifest. Each approved proposal is handed to the change-router for execution. ## Cortex Awareness When the project has a `.cortex/` directory: - **The sibling boundary (both directions).** This skill owns requirement-shaped sources: material that changes what the product should do becomes spec change proposals. The memory-shaped remainder — stakeholders, decisions, domain terms, and the verbatim source itself —