knowledge-discoverylisted

# Knowledge Discovery Answer one question before any other Project Memory work: > What does this repository already believe about itself, and where did each > belief come from? # Core Principle Existing knowledge is scattered across tools never designed to agree - different authors (human or AI), different times, never reconciled. Treat it like five engineers' personal notes on the same system: individually useful, collectively unreliable until cross-checked. Output is NOT the truth about the project. It is: ```text Everything the repository currently claims about itself, where each claim came from, where claims overlap, where claims disagree. ``` Inventory = candidate claims, NOT approved memory. Verification, classification, and reconstruction happen downstream: * verify - `repository-audit` / `codebase-memory` * classify - `knowledge-classification` / `obsolete-knowledge` * design target architecture - `memory-architecture` * edit - `memory-edit` # Mandatory First Step Run this Skill FIRST in any full Project Memory audit, initial memory build, or explicit reconstruction - whenever pre-existing knowledge sources exist. Everything downstream consumes the inventory; skipping it means classifying and editing unverified scattered beliefs blind. # Read-Only Boundary This Skill inventories only. It never: * verifies claims against source code, tests, configuration, build/CI, or Git history * decides Current / Historical / Deprecated / Superseded / Obsolete status