What problem does it solve? Technical documentation drifts out of sync with code as classes are renamed, deleted, or refactored, leaving developers with misleading docs. This Skill enforces mandatory freshness verification before writing or updating any tech doc, so documentation always matches the actual codebase. ## Core Features & Use Cases - Freshness Verification: Runs five pre-write checks covering file existence, deleted class detection, method signature matching, layer/count accuracy, and code-to-doc coverage before any doc is written. - L1-L5 Architecture Organization: Structures docs by architecture layer (GameManager root, Services, Modules, Components, Behaviors) with a root index, module overviews, and per-file sub-module documents. - Stale Doc Marking: Flags outdated docs with a WARNING banner and Last Verified stamp instead of silently deleting them. - Use Case: After refactoring a Unity character locomotion module, ask the AI to update the tech docs — it will verify every referenced .cs file and class still exists, detect renamed classes like LocomotionProfile, and regenerate the module overview with an updated verification stamp. ## Quick Start Write or update the tech documentation for the character module in Assets/Scripts following the L1-L5 layer structure.
