What problem does it solve? New or changing game and creative projects often drift because their core identity is never explicitly defined, stress-tested, or approved, leading to feature creep and contradictory decisions. This Skill structures the process of defining a project's minimal identity contract and prevents unapproved core changes. ## Core Features & Use Cases - Core Proposal and Stress-Testing: Drafts the identity statement, core loop, and central systems, then attacks them with removal, substitution, failure, and expansion counterexamples. - Protection Boundary Classification: Separates elements into INVARIANT, CHANGEABLE, REQUIRES_REAPPROVAL, and OUT_OF_SCOPE so the core never inflates into a feature list. - Approval-Gated State Machine: Tracks states from CORE_SEED through CORE_RECORDED, refusing to mark CORE_CONFIRMED or CORE_RECORDED without explicit user approval. - Use Case: When starting a new game project, use this Skill to define the player promise and core loop, stress-test them against PoC evidence, and record only the user-approved invariants as the binding contract for later development gates. ## Quick Start Help me define and stress-test the core identity contract for my new game project before we commit to any features.
