retrofit-spec

Generate feature specifications from codebase structure and repository context.

1|1|Updated Dec 9, 2025

Search Tags:#documentation #specification #code-analysis #code-to-doc #feature-design #retrofit

Ready to run

npx skills add https://github.com/asermax/claude-plugins --skill retrofit-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrofit-spec
Source: https://github.com/asermax/claude-plugins/tree/main/katachi/skills/retrofit-spec
Command: npx skills add https://github.com/asermax/claude-plugins --skill retrofit-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill extracts and formalizes a missing or ambiguous feature specification from an existing codebase, enabling consistent design documentation and planning.

Core Features & Use Cases

Transform code structure and repository context into a draft feature specification.
Assess scope, boundaries, and acceptance criteria across modules to guide implementation.
Organize the generated spec under docs/feature-specs with retrofit notes and contextual links.

Quick Start

Provide the path to the target codebase or module to generate a draft feature specification.

Frequently Asked Questions about retrofit-spec

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

FAQPage Schema

How do I generate a feature specification from existing code?▼

To generate a feature specification from existing code, provide the path to your target codebase or module. The tool extracts repository context, existing documentation, and code structure to determine scope, boundaries, and acceptance criteria across modules.

Can I extract acceptance criteria from an undocumented codebase?▼

Yes, you can extract acceptance criteria from an undocumented codebase by analyzing its code structure and repository context. This process formalizes missing or ambiguous feature specifications to enable consistent design documentation and planning.

What is the best way to reverse engineer code into design documentation?▼

The best way to reverse engineer code into design documentation is to transform code structure and repository context into a draft feature specification. This approach assesses scope and boundaries across modules to guide implementation.

Where are generated feature specs saved in the repository?▼

Generated feature specs are saved under docs/feature-specs in an appropriate domain or standalone location. The output reflects the repository's conventions and includes retrofit notes with contextual links.

How do I formalize missing feature boundaries across multiple modules?▼

To formalize missing feature boundaries across multiple modules, apply repository context and code structure to determine scope and acceptance criteria. This generates a comprehensive specification that guides consistent implementation.