What problem does it solve?
It helps you create missing design and architecture documentation by deriving intent, mechanics, and system decisions directly from existing implementation instead of guessing.
Core Features & Use Cases
- Reverse-engineers design artifacts: Produces design documents, ADRs, or concept write-ups based on the current code/prototype behavior.
- Extracts mechanics, formulas, and patterns: Identifies gameplay rules for design docs and technical decisions for ADRs (including dependencies and trade-offs).
- Clarifies intent before drafting: Asks targeted questions about “why” to avoid documenting incorrect assumptions.
Use cases: recovering documentation after shipping features, onboarding to an unfamiliar codebase, formalizing a prototype into a structured spec, and documenting architectural decisions from evolving systems.
Quick Start
Ask the skill to reverse-document your current implementation by running: /reverse-document design src/gameplay/magic-system