This skill has a coding agent write a game design document that stays short and stays true to the code. The GDD is one page that says what the game is and indexes its features. Each feature gets its own short design note, with implementation and testing notes added once code exists.
Six modes cover drafting a GDD, writing a new feature, changing one after a playtest, syncing after coding, migrating an existing GDD and recording a decision. A Python checker validates links, statuses and test proof, and an existing GDD in another format is edited in place.
What You Get
- A GDD template of about one page plus design notes for the two or three core-loop features, with unknown values marked [ASSUMPTION]
- Feature templates for design.md, implementation.md and testing.md, and an ARCHITECTURE.md template for shared code
- Six workflow modes: draft, new feature, change, sync after coding, migrate and record a decision
- A decision row format with IDs, alternatives and evidence, and proof annotations for ticked criteria
- A checker script with error and warning codes for broken links, missing design files and status mismatches
- A gotcha list covering over-long drafts, empty templates, unasked extras and restructured GDDs
Common Use Cases
- Drafting a one-page GDD from a pitch or planning chat
- Updating a feature note after a playtest changed a number
- Syncing docs after a feature is coded
- Splitting a long GDD into a feature index and notes without losing text
What Makes It Unique
The skill keeps each fact in one home and links everywhere else, and it treats a test’s assertions, not its name, as proof for a ticked criterion. It edits a GDD in its own format when the project does not use this layout, and its checker can compare a migrated GDD against a saved copy to show any line that went missing.
Under The Hood
The agent loads the SKILL.md and reads the mode, rules and template references for the chosen task. It searches the project for existing docs, reads the conversation and, when code exists, the repo and git diff or log. It writes and edits Markdown files in your docs folder and runs a bundled Python checker, which the script describes as read-only with no network use and no other programs. For a migration it saves a copy of the old GDD outside the docs folder. It does not commit unless asked.