tkm:rebuild-spec

Reverse-engineer source code into architecture, data models, and API specifications.

Updated May 13, 2026
One-click install
npx skills add https://github.com/khapn-2933/agentic-coding-hands-on --skill tkm-rebuild-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tkm:rebuild-spec
Source: https://github.com/khapn-2933/agentic-coding-hands-on/tree/main/.claude/skills/rebuild-spec
Command: npx skills add https://github.com/khapn-2933/agentic-coding-hands-on --skill tkm-rebuild-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps reverse-engineer existing codebases into structured documentation, including architecture, data models, API specs, and more, saving time and ensuring comprehensive documentation.

Core Features & Use Cases

  • Reverse-Engineering: Automatically generate documentation from source code.
  • Structured Artifacts: Generates 9 standard doc artifacts (architecture, data models, API specs, etc.) plus per-feature specifications.
  • Parallel Agents: Utilizes scanner, researcher, reviewer, and doc-writer agents for efficient processing.
  • Use Case: Ideal for teams looking to create detailed documentation of their codebase without manual effort.

Quick Start

Run the command: /tkm:rebuild-spec to start the documentation process for your codebase.

Frequently Asked Questions about tkm:rebuild-spec

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

FAQPage Schema
How do I reverse-engineer a codebase into structured technical documentation?▼

Generating structured documentation from source code involves scanning the codebase to extract architecture, data models, and API specifications. This Skill uses parallel agents to automatically reverse-engineer these structured artifacts without manual effort.

What types of documentation artifacts can I automatically generate from source code?▼

Automatically generating documentation from source code yields 9 standard artifacts including architecture, data models, and API specifications. It also creates detailed per-feature specifications for comprehensive codebase coverage.

Does automated codebase documentation work without any dependencies?▼

Automated codebase documentation requires no external dependencies, but your source code must be present and structured in a way that can be scanned and analyzed by the specialized parallel agents.

What is the best way to document an existing codebase without manual effort?▼

Using parallel processing agents is the best way to document an existing codebase without manual effort. Scanner, researcher, reviewer, and doc-writer agents collaborate to reverse-engineer source code into structured technical documentation.

How do parallel agents process source code to create API specifications and data models?▼

Parallel agents process source code by dividing reverse-engineering tasks among scanner, researcher, reviewer, and doc-writer components. This specialized workflow extracts and structures API specifications and data models efficiently.

When should I not use automated reverse-engineering for codebase documentation?▼

Avoid automated reverse-engineering for codebase documentation if your source code is not present or is structured in a way that cannot be easily scanned and analyzed by the parallel agents to extract architecture and API specs.