reverse-document

To generate architecture documentation from source code, this Skill parses existing codebases and prototypes to extract design decisions and dependencies, organizing them into structured ADRs or design docs after collaborative clarifications.

Reverse engineering a GDD from prototype code involves parsing source paths like src/gameplay to map implementation details to design artifacts, delivering templated concept documents with clear rationale after anchoring intent.

Yes, you can produce ADRs for outdated documentation in src/core by analyzing the existing code to extract key architectural decisions, mapping those decisions to structured templates with clear rationale.

Documenting legacy code without original rationale requires reverse-engineering the implementation to infer decisions, then using collaborative clarifications to anchor intent before drafting templated design or architecture artifacts.

Yes, this code analysis approach works for both by parsing code and prototypes to map implementation details into either GDDs for gameplay systems or ADRs for core software architecture, delivering structured outputs.

You should avoid reverse-engineering code to generate design docs when the source code is heavily obfuscated or lacks coherent structure, as parsing relies on readable implementation logic to extract accurate design decisions.