What problem does it solve? When adopting a documentation pipeline on a project that was already built without one, there is no source of truth except the code itself. This Skill reverse-engineers documentation from an existing Unity project without modifying anything, so the pipeline starts from facts rather than guesses. ## Core Features & Use Cases - Code-to-docs scanning: Reads ProjectSettings, manifest.json, the Assets/ tree, script filenames, and ScriptableObject configs in a cheap-to-expensive order to map systems without burning context. - Mechanics documentation: Creates one doc per discovered system in docs/mechanics/ with status implemented and actual numbers read from configs, describing how things work now rather than how they should. - Backlog generation: Converts found TODOs, unfinished systems, and placeholders into backlog tasks, marking AI-discovered items with origin: ai and design-blocking ones with needs-design. - Use Case: You have a half-finished Unity RTS with no docs. Run /adopt once to get a project map, per-system mechanics docs with real balance numbers, a backlog of unfinished work, and a batched list of questions about vision and scope that code cannot answer. ## Quick Start Run the /adopt command to scan this existing Unity project and generate its documentation and backlog from the code.
