reverse-engineer-specs-architecture

Reverse engineer codebases into architectural documentation and functional specifications.

Updated May 6, 2026
One-click install
npx skills add https://github.com/johan-Rm/agents --skill reverse-engineer-specs-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-engineer-specs-architecture
Source: https://github.com/johan-Rm/agents/tree/main/skills/reverse-engineer-specs-architecture
Command: npx skills add https://github.com/johan-Rm/agents --skill reverse-engineer-specs-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of understanding undocumented or legacy codebases by systematically extracting architectural patterns, structural invariants, and functional specifications directly from the source.

Core Features & Use Cases

  • Architectural Mapping: Automatically identifies layers, responsibilities, and data flows within a project.
  • Spec Derivation: Generates actionable specifications based on existing code behavior rather than theoretical assumptions.
  • Use Case: Use this skill when taking over a legacy project to quickly produce a high-level architecture note and a list of functional specs without manually auditing every file.

Quick Start

Invoke the reverse-engineer-specs-architecture skill to analyze the current repository and generate a comprehensive architecture note.

Frequently Asked Questions about reverse-engineer-specs-architecture

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

FAQPage Schema
How do I generate architecture documentation for an undocumented legacy codebase?

To generate architecture documentation for an undocumented codebase, this skill analyzes repository structure, layer boundaries, and existing source files to infer system invariants and extract functional specifications automatically.

What is the best way to derive functional specifications from existing code behavior?

Deriving functional specifications from existing code behavior involves systematically extracting architectural patterns and structural invariants directly from the source to produce evidence-based outputs rather than theoretical assumptions.

Can I use code analysis to identify technical debt and architectural patterns in a project?

Yes, code analysis identifies technical debt and architectural patterns by examining repository structure and layer boundaries to map data flows and infer system invariants from existing source files.

Do I need to provide internal documentation references to reverse engineer project architecture?

Yes, providing internal documentation references is required to reverse engineer project architecture accurately, as the skill relies on access to project source files and documentation to produce evidence-based outputs.

What are the limitations of reverse engineering architectural mapping for refactoring?

The limitation of reverse engineering architectural mapping for refactoring is that it relies on existing source files and documentation references, meaning heavily obfuscated or incomplete codebases may yield less accurate functional specifications.