spec-miner

Extract software specifications from codebases using EARS format.

Updated Mar 7, 2026

Search Tags:#code analysis #documentation #specification #codebase exploration #reverse engineering #legacy systems

Ready to run

npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill spec-miner-shalevamin

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you understand and document complex or undocumented codebases, making it easier to work with legacy systems, onboard new team members, or plan future enhancements.

Core Features & Use Cases

Codebase Exploration: Maps code dependencies, traces data flows, and identifies key modules.
Specification Generation: Creates documentation in EARS format from existing code.
Use Case: You've inherited a decade-old Python project with no documentation. Use this Skill to explore its structure, identify API endpoints, and generate a foundational specification document.

Quick Start

Use the spec-miner skill to reverse engineer the codebase located in the '/app/backend' directory.

Frequently Asked Questions about spec-miner

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

FAQPage Schema

How do I document an undocumented legacy codebase?▼

To document an undocumented legacy codebase, you extract software specifications by mapping code dependencies, tracing data flows, and documenting observed behaviors in EARS format. This reverse engineers inherited projects into foundational architecture and API documentation.

What is the best way to reverse engineer specifications from existing code?▼

The best way to reverse engineer specifications from existing code is to map module dependencies, trace data flows, and identify key APIs. Using Glob, Grep, and Read tools for codebase exploration accurately documents the observed behaviors.

Can I generate EARS format documentation for an inherited project?▼

Yes, you can generate EARS format documentation for an inherited project by analyzing the codebase to extract observed behaviors. This maps underlying data flows and dependencies directly into structured software specifications.

How do I trace data flows and map dependencies in a complex codebase?▼

You trace data flows and map dependencies in a complex codebase by using exploration tools like Glob, Grep, and Read to analyze source code. This identifies key modules and reconstructs the architectural relationships.

Does codebase exploration work for identifying API endpoints in legacy systems?▼

Yes, codebase exploration works for identifying API endpoints in legacy systems by analyzing existing source code structure. It traces data flows and maps dependencies to reveal undocumented APIs and business logic.

When should I not use automated code analysis for specification generation?▼

You should not use automated code analysis for specification generation when the codebase lacks accessible source code or when precise runtime behavior cannot be statically determined. It works best for inherited projects requiring foundational reverse engineering.