spec-miner

Reverse-engineer codebases to generate specifications and documentation.

2|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Axel-DaMage/opencode-config --skill spec-miner-axel-damage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-miner
Source: https://github.com/Axel-DaMage/opencode-config/tree/main/skills/spec-miner
Command: npx skills add https://github.com/Axel-DaMage/opencode-config --skill spec-miner-axel-damage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires read, grep, glob, bash, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The spec-miner Skill solves the challenge of understanding and documenting existing codebases, particularly those with no or limited documentation. It aids in reverse-engineering, onboarding to new projects, and enhancing existing features.

Core Features & Use Cases

  • Reverse-Engineering: Extract specifications from legacy or undocumented systems.
  • Documentation Generation: Create API documentation and map code dependencies.
  • Analysis: Identify undocumented business logic and create architecture documentation.
  • Use Case: A developer takes over a new project with no documentation. The spec-miner Skill is used to generate a detailed specification for the project, which helps in understanding and enhancing the code.

Quick Start

To begin the reverse-engineering process, activate the spec-miner Skill and provide the codebase directory as input.

Frequently Asked Questions about spec-miner

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

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

To generate documentation for an undocumented legacy codebase, you can automate the reverse-engineering process to extract specifications, identify dependencies, and map business logic. This provides a structured framework for understanding and documenting existing code.

What is the best way to reverse-engineer code to extract business logic specifications?

Reverse-engineering code to extract business logic specifications is best handled by automating the analysis of the codebase to identify core dependencies and undocumented logic. This approach systematically maps the architecture and generates detailed specification documents.

Can I analyze code dependencies and map architecture without existing documentation?

Yes, you can analyze code dependencies and map architecture without existing documentation by using automated reverse-engineering techniques. The process identifies structural relationships and business logic, creating a comprehensive specification from the raw source code.

Do I need Python scripting and bash tools to extract specifications from source code?

Yes, extracting specifications from source code requires Python scripting and tools like grep, glob, read, and bash. These dependencies are necessary to automate the file searching, pattern matching, and code analysis required for reverse-engineering the codebase.

How do I onboard to a new project with no documentation using code analysis?

To onboard to a new project with no documentation, use code analysis to reverse-engineer the codebase and generate a detailed project specification. This highlights dependencies and business logic, accelerating your understanding of the system architecture.

What are the limitations of automating specification generation for legacy systems?

Automating specification generation for legacy systems relies on analyzing raw source code with tools like grep and bash, meaning it is limited by code obfuscation, missing files, and dynamically loaded logic that may not be statically discoverable in the directory.