methodology-intakelisted

> ## DEPRECATED (2026-09-09) > > **Do not invoke this skill.** Flagged by its maintainer as outdated and not fit for its stated > purpose. Its decision — "should this external material change repo artifacts, and which one?" — > now lives in `baseline-gap-review`, which has a fuller placement heuristic (baselines / skills / > flows / hooks / Glossary, across two independent axes) plus an activation test this skill never > had. > > It also predates the conventions around it: the frontmatter above was missing `status`, > `maintainer`, `problem` and `when-not-to-use` until this notice was added, and its own > "Skill Admission Gate" section now overlaps `process-vs-work-doctrine` rule 1. > > **Not removed, because it is load-bearing in ~10 places** — `CLAUDE.md`, `AGENTS.md`, > `CONTEXT.md`, `baselines/process-vs-work-doctrine/baseline.md`, `bookshelf/INDEX.md`, > `docs/intake.md` (its own verdict ledger), and `docs/specs/0005-capture-input-note-vs-methodology-intake.md`. > Deleting the folder alone would leave every one of those dangling and orphan the ledger. Removal > is its own pass, via `skill-lifecycle`; this notice is the safe first step. # 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