spec-miner

Name: spec-miner
Availability: InStock
Author: camelranchentertainment

Extract specifications, dependencies, and architectural decisions from codebases.

1|Updated Jan 19, 2026

Search Tags:#architecture #documentation #specification #legacy #code-analysis #dependency-mapping #reverse-engineering

Ready to run

npx skills add https://github.com/camelranchentertainment/Booking-Platform --skill spec-miner-camelranchentertainment

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-miner
Source: https://github.com/camelranchentertainment/Booking-Platform/tree/main/.claude/skills/spec-miner
Command: npx skills add https://github.com/camelranchentertainment/Booking-Platform --skill spec-miner-camelranchentertainment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legacy, undocumented, or inherited codebases often lack reliable specifications. Spec Miner helps you map dependencies, generate API documentation from source, identify undocumented business logic, and understand what the code actually does so you can create accurate architecture documentation.

Core Features & Use Cases

Dependency mapping: identify modules, libraries, and interfaces across the codebase.
API documentation generation: produce up-to-date API specs from source.
Undocumented logic discovery: surface hidden business rules and data flows.
Architecture documentation: translate implementation details into architecture diagrams and narratives.

Quick Start

Analyze a target repository to extract specifications and produce a structured specification.

Frequently Asked Questions about spec-miner

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

FAQPage Schema

How do I extract specifications from an undocumented legacy codebase?▼

To extract specifications from an undocumented legacy codebase, analyze the source code to map modules, APIs, and data flows. This process surfaces hidden business rules and translates implementation details into a structured specification with architecture notes.

What is the best way to generate API documentation from existing source code?▼

Generating API documentation from existing source code involves analyzing the repository to identify interfaces and dependencies. This reverse-engineering approach captures observed requirements and code locations to produce up-to-date API specs for inherited projects.

How do I map dependencies and data flows in an inherited project?▼

Mapping dependencies and data flows in an inherited project requires scanning the codebase to identify modules, libraries, and interfaces. This dependency mapping reveals architectural decisions and hidden business logic to replace missing documentation.

Can I reverse engineer architecture decisions from a codebase with missing documentation?▼

Yes, you can reverse engineer architecture decisions from a codebase with missing documentation by applying code analysis to identify observed requirements. This delivers a structured specification detailing architecture notes and code locations for future maintenance.

When do I need to reverse engineer business rules from source code?▼

You need to reverse engineer business rules from source code when working with legacy or inherited systems lacking reliable specifications. This code analysis extracts undocumented logic and data flows to create accurate architecture documentation.

What are the limitations of extracting architecture documentation directly from code?▼

Extracting architecture documentation directly from code is limited to observed requirements and implementation details rather than original design intent. It maps existing modules and APIs but may not capture external context or undocumented edge cases.