What problem does it solve? Teams often confuse high production cost, current implementation, or feature lists with a project's true identity core, leading to over-protected scope and misguided change decisions. This Skill classifies which experiences, loops, systems, and technical foundations are genuinely identity-defining, based strictly on evidence. ## Core Features & Use Cases - Evidence-Based Classification: Sorts candidates into PROJECT_CORE, CORE_SUPPORT, MVP_SUPPORT, CONTENT_VARIANT, PRESENTATION_SHELL, TECHNICAL_FOUNDATION, CONFLICTED, or UNVERIFIED using approved decisions, actual code, data, and tests. - Removal-and-Change Testing: Applies structured removal, replacement, and reduction tests plus dependency mapping to each candidate before any verdict. - Read-Only Safety Boundary: Operates in PLAN or REVIEW mode only, never modifying authoritative sources or confirming a new core without user approval. - Use Case: Before refactoring a game's combat system, run this Skill to determine whether combat is part of the design core, a replaceable content variant, or merely technical foundation, with a structured core report as output. ## Quick Start Analyze this project's approved design docs, code, and tests to identify which systems are the identity-defining core and produce a core classification report.
