Agent skill · Backend & API

spec-miner

Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.

Jeffallangithub.com/JeffallanGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add Jeffallan/claude-skills --skill spec-miner --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 4 KB
Bundled scripts: none
Version: 1.1.0
Declared author: https://github.com/Jeffallan
Allowed tools: ReadGrepGlobBash
Path: skills/spec-miner/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 10,871 · +100 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Spec Miner Reverse-engineering specialist who extracts specifications from existing codebases. ## Role Definition You operate with two perspectives: **Arch Hat** for system architecture and data flows, and **QA Hat** for observable behaviors and edge cases. ## When to Use This Skill - Understanding legacy or undocumented systems - Creating documentation for existing code - Onboarding to a new codebase - Planning enhancements to existing features - Extracting requirements from implementation ## Core Workflow 1. **Scope** - Identify analysis boundaries (full system or specific feature) 2. **Explore** - Map structure using Glob, Grep, Read tools - _Validation checkpoint:_ Confirm sufficient file coverage before proceeding. If key entry points, configuration files, or core modules remain unread, continue exploration before writing documentation. 3. **Trace** - Follow data flows and request paths 4. **Document** - Write observed requirements in EARS format 5. **Flag** - Mark areas needing clarification ### Example Exploration Patterns ``` # Find entry points and public interfaces Glob('**/*.py', exclude=['**/test*', '**/__pycache__/**']) # Locate technical debt markers Grep('TODO|FIXM

What's inside
Steps it walks through
  1. Role Definition
  2. When to Use This Skill
  3. Core Workflow
  4. Example Exploration Patterns
  5. EARS Format Quick Reference
  6. Reference Guide
  7. Constraints
  8. MUST DO
  9. MUST NOT DO
  10. Output Templates
Ships with 4 files
  • references/analysis-checklist.md
  • references/analysis-process.md
  • references/ears-format.md
  • references/specification-template.md
More from claude-skills
All skills →
About this skill
What does the spec-miner skill do?

Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.

How do I install it?

Run `npx skills add Jeffallan/claude-skills --skill spec-miner --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going