spec-miner

Extract EARS-formatted specifications and analysis reports from legacy codebases.

Updated Feb 11, 2026

Search Tags:#architecture #documentation #specifications #code-analysis #reverse-engineering #legacy-code #ears-format

Ready to run

npx skills add https://github.com/lamb92009/claude-skills --skill spec-miner-lamb92009

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legacy or undocumented systems often lack clear specifications, making maintenance and onboarding error-prone. Spec Miner helps teams extract actionable requirements directly from existing code and artifacts.

Core Features & Use Cases

Scope identification: Determine analysis boundaries for a given project or feature.
Exploration & mapping: Use Glob, Grep, Read to map structure and data flows.
Documentation generation: Produce a reverse-engineered specification document with EARS-style observations.

Quick Start

Provide a starting scope and run the analysis workflow to generate a reverse-spec document.

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 legacy code that has no documentation?▼

Extract specifications from undocumented legacy code by mapping structure and data flows to generate EARS-formatted observations and a structured specification document. This reverse-engineering process yields an analysis report suitable for documentation and stakeholder review.

What is EARS format for reverse-engineering software requirements?▼

EARS format structures requirements observations extracted from legacy code. Spec Miner applies EARS format to reverse-engineer undocumented systems, producing actionable specifications that clarify maintenance and onboarding for stakeholders.

How do I generate documentation for an undocumented codebase during onboarding?▼

Generate documentation for an undocumented codebase by defining a starting scope and running an analysis workflow. This maps structure and data flows, producing a reverse-engineered specification document with EARS-style observations suitable for onboarding and stakeholder review.

Can I use code analysis to investigate features in a legacy system?▼

Code analysis supports feature investigations in legacy systems by mapping data flows and structure within defined boundaries. This exploration produces EARS-formatted observations and a structured specification clarifying feature behavior without existing documentation.

What's the best way to reverse-engineer requirements from existing code artifacts?▼

Reverse-engineer requirements from existing code artifacts by defining analysis boundaries and exploring structure and data flows. This generates EARS-style observations and a structured specification document, making maintenance and onboarding less error-prone.

When should I not use reverse-engineering to extract specifications?▼

Avoid extracting specifications via reverse-engineering when a codebase already has clear specifications. Spec Miner targets undocumented or legacy systems lacking clear requirements, ensuring maintenance and onboarding efforts are not redundant or error-prone.