What problem does it solve? Turning free-form game ideas into actionable documentation is hard: raw concept notes are ambiguous, and filling gaps with assumptions leads to building the wrong game. This Skill structures the intake process so every design decision comes from the user, not from the AI's guesses. ## Core Features & Use Cases - Batched Questioning: Reads all unprocessed files in concept/ first, then asks one numbered batch of questions, each with 2-3 concrete options and a recommendation. - Adaptive Documentation Set: Creates only the docs the project needs — vision and scope boundaries are mandatory, mechanics docs are created per independent system with statuses (accepted/proposed). - Delta Handling: When the user changes their mind mid-project, it reports what breaks (docs, code systems, tasks) before rewriting anything, and logs changes in docs/CHANGELOG.md. - Use Case: A solo game developer dumps scattered notes into concept/ and runs /intake; the Skill produces a vision doc, scope boundaries, per-mechanic docs with concrete numbers, and a deferred-questions list — ready to derive tasks from. ## Quick Start Ask the AI to run the intake process on the files in the concept folder and turn them into project documentation.
