Skip to content
SkillScript-led2,227 tokens in use

game-docs

Write and maintain a game's design docs: a one-page GDD, short per-feature notes and a read-only checker for links, statuses and test proof.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/workflows/game-docs
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing game-docs costs

94tokens idle
2,227tokens in use
8,218tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/check_docs.py.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure25/25
  • Examples9/15
  • Output15/15
  • Size15/15
  • Resources12/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 41
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 41

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers