One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill reverse-document-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-document
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/reverse-document
Command: npx skills add https://github.com/MichaelSolati/mkai --skill reverse-document-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of missing documentation for existing game code, prototypes, or implemented features that were built without initial planning documents, or for inherited codebases that lack any formal documentation.

Core Features & Use Cases

  • Reverse-Engineer Game Design Docs: Generate game design document (GDD) sections directly from existing gameplay code, capturing mechanics, formulas, rules, and edge cases.
  • Generate Architecture Decision Records: Create ADRs from core system code, documenting technical patterns, decisions, trade-offs, and performance characteristics.
  • Prototype Concept Documentation: Turn game prototypes into formal concept documents, capturing core mechanics, emergent gameplay, and technical feasibility insights.
  • Use Case: Game developers who built a feature without writing a design doc first, or inherited a codebase with no documentation, can use this Skill to formalize existing implementation in minutes.

Quick Start

Use the reverse-document skill to generate a design document for the combat system located in the src/gameplay/combat directory.

Frequently Asked Questions about reverse-document

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a game design document from existing source code?

To generate a game design document from source code, you analyze the implementation to extract mechanics, formulas, and rules, then combine them with user-clarified design intent to formalize the structured document.

Can I create architecture decision records for an inherited codebase with no documentation?

You can create architecture decision records for an undocumented inherited codebase by analyzing core system code to identify technical patterns, trade-offs, and performance characteristics automatically.

What is the best way to document a game prototype that was built without initial planning?

The best way to document an unplanned game prototype is to reverse-engineer the implementation into a formal concept document, capturing core mechanics, emergent gameplay, and technical feasibility insights.

Does generating design docs from code work for specific gameplay systems like combat?

Generating design docs from code works for specific systems like combat by analyzing the targeted implementation directory to extract mechanics, edge cases, and technical patterns directly into the document.

Do I need to provide input when reverse-engineering code into design documentation?

You need to provide clarified design intent as input when reverse-engineering code, because the Skill combines your input with the extracted technical patterns to generate the final design artifacts.