skills.rest
Estom
EstomCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-miner

Extract EARS-format specifications from legacy codebases using Read, Grep, Glob, and Bash.

Updated Mar 17, 2026
Search Tags:#documentation#specification#code-analysis#reverse-engineering#legacy-code#ears-format#glob-grep-read
One-click install
npx skills add https://github.com/Estom/aiflex --skill spec-miner-estom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-miner
Source: https://github.com/Estom/aiflex/tree/main/skills-repo/Jeffallan-skills/spec-miner
Command: npx skills add https://github.com/Estom/aiflex --skill spec-miner-estom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legacy codebases often lack up-to-date documentation, making it hard to understand behavior, data flows, and requirements. Spec Miner helps you systematically extract actionable specifications from existing implementations.

Core Features & Use Cases

  • Code archaeology: map structure, identify data models, and trace observable behaviors.
  • Documentation generation: produce EARS-formatted requirements and concise docs from code evidence.
  • Onboarding and maintenance: accelerate understanding of unfamiliar systems, and plan feature enhancements using observed constraints.

Quick Start

Analyze a target repository to generate a reverse specification document from observed code.

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 a legacy codebase with no documentation?▼

To generate documentation from legacy code, you analyze the repository to map structure and trace data flows. This produces concise, EARS-formatted requirements derived directly from code evidence, supporting structured documentation workflows for undocumented features.

What is EARS format and when is it needed for code analysis?▼

EARS format is a structured syntax for writing requirement-style specifications. It is needed during code analysis and architecture retrospectives to transform observed code behaviors and constraints into precise, unambiguous requirement artifacts for onboarding and maintenance.

How to reverse engineer requirements from existing source code?▼

Reverse engineer requirements from existing source code by tracing data flows and identifying observable behaviors. Using evidence-based code analysis, you map the system structure and generate structured requirement artifacts that reflect the actual implementation logic.

Does spec mining work for accelerating onboarding to unfamiliar codebases?▼

Spec mining accelerates onboarding to unfamiliar codebases by mapping structural architecture and tracing data flows. It generates concise documentation and EARS-formatted requirement artifacts from observed code constraints, helping new developers understand system behavior quickly.

What is the best way to document undocumented features in legacy code?▼

The best way to document undocumented features is through code archaeology, mapping data models and tracing observable behaviors. This evidence-based approach generates EARS-formatted requirements directly from the implementation's actual constraints and data flows.

Related Skills

Explore More Software Engineering Skills→
UnaMentisUnaMentis
6

read-external

Read files from configured external repositories using absolute paths.

Official
Basic
mimikunmimikun

kiro-spec-requirements

Convert project descriptions into structured EARS requirements for review.

Community
Intermediate
raybirdraybird
1

gitnexus-refactoring

Rename, extract, and split code symbols using GitNexus CLI graph analysis.

Community
Advanced
JeffallanJeffallan
10.9k

spec-miner

Extract undocumented functionality from codebases into EARS-formatted specifications.

Community
Advanced