specflow-ingestlisted

# Specflow: Document Ingest 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 — is NOT dropped: hand it off to the `cortex-archive-ingest` skill, which preserves the source under `.cortex/archive/documents/<slug>/` and extracts schema-conformant atlas entries via its atlas strategy. Conversely, when `cortex-archive-ingest` encounters requirement-shaped material, it hands off here. - **Business specs alongside atlas cross-references (design §8.4 bridge 2).** A manifest entry that proposes a new business spec also names the `.cortex/atlas/decisions/` entry it corresponds to (created via the `cortex-archive-ingest` handoff), so the outcome ("what user outcome we serve") and the decision ("why we chose this approach") cross-reference each other. - **Query insight before proposing spec changes (when `.cortex/insight/` exists).** Before a