spec-miner

Extract technical specifications and EARS-compliant requirements from legacy codebases.

9|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/stephanj/claude-code-collections --skill spec-miner-stephanj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-miner
Source: https://github.com/stephanj/claude-code-collections/tree/main/skills/spec-miner
Command: npx skills add https://github.com/stephanj/claude-code-collections --skill spec-miner-stephanj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of working with undocumented or legacy codebases by systematically extracting architectural patterns, business logic, and requirements.

Core Features & Use Cases

  • Automated Archaeology: Uses static analysis tools to map entry points, data models, and API surfaces.
  • Standardized Documentation: Converts observed code behaviors into formal EARS (Easy Approach to Requirements Syntax) specifications.
  • Use Case: When joining a project with no documentation, use this skill to generate a comprehensive specification document that outlines the tech stack, data flows, and acceptance criteria for existing features.

Quick Start

Invoke the spec-miner skill to analyze the current directory and generate a reverse-engineered specification document for the existing system.

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 a legacy codebase, use static analysis to map architecture and data flows, extracting functional requirements to create formal specification documents.

What is the best way to reverse-engineer software architecture from existing code?

Reverse-engineering software architecture involves using static analysis and pattern recognition to map entry points and data models, converting observed behaviors into clear architectural summaries.

How do I extract functional requirements from source code?

Extracting functional requirements from source code uses static analysis to identify business logic and system behaviors, automatically translating them into formal EARS-compliant requirement specifications.

Can I use static analysis to map data flows in legacy code?

Static analysis effectively maps data flows in legacy code by identifying API surfaces and data models, providing the architectural summaries needed to understand complex, undocumented system behaviors.

What are the limitations of automated code archaeology for generating specs?

Automated code archaeology relies on static analysis and pattern recognition, which may miss dynamic runtime behaviors or complex dependencies in legacy code, potentially limiting generated specification accuracy.