How does the skill identify architectural decisions?

It uses a codebase analyzer to detect recurring patterns and logical choices in your code, then recommends whether they should be documented as Architecture Decision Records (ADR) or Design Patterns (DES).

Will it overwrite my existing README.md?

No. The skill is designed to complement existing READMEs by extracting high-level vision and goals into separate files while leaving installation and usage instructions in the README.

What does it mean to 'retrofit' a codebase?

Retrofitting is the process of generating formal documentation—such as specifications, designs, and decision records—from code that has already been implemented, allowing legacy projects to adopt modern framework standards.

Does this skill work with large-scale projects?

Yes, it includes specific migration paths for large projects (20+ modules) that focus on a 'skeleton and critical path' approach to avoid documentation overhead.

Retrofit Documentation & Specs

Name: Retrofit Documentation & Specs
Author: asermax

byasermax

•

Learning & Documentation

Generates framework documentation, feature specifications, and architectural decisions directly from existing codebases.

About

The Retrofit Existing skill is designed to bridge the gap between undocumented legacy code and structured development frameworks. By analyzing existing implementations, it helps developers infer requirements, document architectural decisions (ADRs), and create design specifications without manual rewriting. It is ideal for teams looking to adopt formal documentation standards gradually, ensuring that existing institutional knowledge is preserved while improving codebase maintainability through automated discovery and indexing.

Key Features

Discovery and documentation of architectural decisions (ADR) and patterns (DES)
1 GitHub stars
Seamless integration with FEATURES.md and project tracking structures
Automated specification generation from existing module logic
Inference of data flows and modeling for comprehensive design docs
Support for multiple migration strategies from top-down to bottom-up

Use Cases

Onboarding existing codebases into the Katachi framework structure
Documenting legacy systems that lack formal technical specifications
Standardizing architectural decision records in established projects

About

Key Features

Discovery and documentation of architectural decisions (ADR) and patterns (DES)
1 GitHub stars
Seamless integration with FEATURES.md and project tracking structures
Automated specification generation from existing module logic
Inference of data flows and modeling for comprehensive design docs
Support for multiple migration strategies from top-down to bottom-up

Use Cases

Onboarding existing codebases into the Katachi framework structure
Documenting legacy systems that lack formal technical specifications
Standardizing architectural decision records in established projects