methodology-intakelisted

# Methodology Intake Use this as a read-only classifier before turning external methodology sources into repo artifacts. Do not create or modify skills, specs, ADRs, issues, or glossary terms during intake unless the user explicitly asks for the follow-up work after reviewing the report. ## Inputs - External methodology source: article, repository, X thread, paper, tool list, framework, workflow, or public discussion. - Optional captured input note from `capture-input-note`. - Optional user goal: learn, critique, adapt, implement, reject, or park. ## Workflow 1. Read the source, captured input note, or provided excerpt closely enough to classify it. 2. Check current repo language in `CONTEXT.md` and relevant roadmap/spec docs. 3. Produce one Markdown methodology intake report. 4. Assign exactly one primary intake destination. 5. Assign exactly one retention status. 6. Explain why the other destinations were not selected. 7. If implementation is recommended, name the minimum vertical slice and verification. 8. If retention is `parked` or `revisit-on-trigger`, record a dated one-line verdict (source, destination, retention, trigger) in the repo's intake ledger — in this repo, `docs/intake.md`. The verdict line is part of the intake output, not follow-up work; do not write anything else there. ## Destinations Use exactly one primary destination: - `Rule`: A judgment principle that can be absorbed into an existing workflow. - `Skill`: A repeatable workflo