retrofit-decision

Generate ADR or DES drafts documenting architectural decisions from codebases.

1|1|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/asermax/claude-plugins --skill retrofit-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrofit-decision
Source: https://github.com/asermax/claude-plugins/tree/main/katachi/skills/retrofit-decision
Command: npx skills add https://github.com/asermax/claude-plugins --skill retrofit-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documenting existing architectural decisions and design patterns from a codebase as ADRs or DES to preserve rationale and facilitate future changes.

Core Features & Use Cases

  • Create ADRs for one-time architectural choices discovered in codebases or update existing ADRs with clarified rationale.
  • Generate a DES when a repeatable design pattern is used across multiple modules, with references to code examples and decision indexes.
  • Reference relevant project documentation guides and provide a ready-to-review draft for inclusion in docs/design or docs/architecture.

Quick Start

Provide the topic and I will generate a draft ADR or DES documenting the current rationale and references.

Frequently Asked Questions about retrofit-decision

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

FAQPage Schema
How do I document existing architectural decisions in a codebase?

To document existing architectural decisions, you generate draft Architecture Decision Records (ADRs) capturing the rationale behind established codebase choices. This Skill analyzes your code and outputs ready-to-review ADR drafts to the docs/architecture directory.

What is the best way to document repeatable design patterns from code?

The best way to document repeatable design patterns is by generating a Design Example Snippet (DES). This process creates drafts referencing code examples and decision indexes, saving the output directly to the docs/design directory for future reference.

When should I create an ADR versus a DES for my software architecture?

You should create an ADR for one-time architectural choices discovered in your codebase, while a DES is appropriate when a repeatable design pattern is used across multiple modules. Both document rationale to facilitate future codebase changes.

Can I update existing ADRs with clarified rationale from an established codebase?

Yes, you can update existing ADRs with clarified rationale. By applying this process to codebases with established decisions, it loads relevant guidance and templates to produce ready-to-review drafts that clarify the original architectural context.

Do I need specific templates to generate architecture documentation for my project?

You do not need to manually provide templates to generate architecture documentation. The process automatically loads relevant project documentation guides and templates, then outputs structured drafts to docs/architecture/ADR-*.md or docs/design/DES-*.md.