read-the-docs-firstlisted

# Read The Docs First ## Purpose Prevent unsupported claims about tools, APIs, frameworks, and repo decisions. ## Preserves Source-based reasoning. ## Required Evidence - Claim, plan, or task that depends on documented behavior. - Local docs, ADRs, schemas, interfaces, or primary upstream sources. - Version or date when external behavior may have changed. ## Failure Signs - Memory is cited as documentation. - Inference is presented as a source-backed fact. - A docs gap is hidden instead of named. ## When To Use - The task depends on external API, framework, CLI, or runtime behavior. - The repo may already document a decision in `CONTEXT.md`, ADRs, schemas, or interfaces. - The user states a rule or convention that could be outdated. - AI proposes behavior without citing a primary source. ## When Not To Use - Purely local refactors whose behavior is fully determined by code. - Cases where the user supplied the authoritative source in the prompt. - Cases where no docs exist and code is explicitly the source of truth. ## Inputs Expected - Claim, plan, or task that depends on documented behavior. - Relevant repo files, docs, ADRs, package names, API names, or version constraints. - Whether external browsing is allowed when upstream docs are needed. ## Output Expected ```md Sources checked: Relevant constraints: Inference: Docs gap: Next action: ``` ## Process 1. Check local `CONTEXT.md`, `CONTEXT-MAP.md`, `docs/adr/`, README files, schemas, and interface definit