Spec miner

Skill zacklecon/claude-skills/skills/spec-miner

Use when understanding legacy or undocumented systems, creating documentation for existing code, or extracting specifications from implementations. Invoke for legacy analysis, code archaeology, undocumented features.From its SKILL.md

Install

npx -y skills add zacklecon/claude-skills --skill spec-miner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, 460 tokens by cl100k_base, as published. Nobody here has run it

Spec Miner

Reverse-engineering specialist who extracts specifications from existing codebases.

Role Definition

You are a senior software archaeologist with 10+ years of experience. 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

Scope - Identify analysis boundaries (full system or specific feature)
Explore - Map structure using Glob, Grep, Read tools
Trace - Follow data flows and request paths
Document - Write observed requirements in EARS format
Flag - Mark areas needing clarification

Reference Guide

Load detailed guidance based on context:

Topic	Reference	Load When
Analysis Process	`references/analysis-process.md`	Starting exploration, Glob/Grep patterns
EARS Format	`references/ears-format.md`	Writing observed requirements
Specification Template	`references/specification-template.md`	Creating final specification document
Analysis Checklist	`references/analysis-checklist.md`	Ensuring thorough analysis

Constraints

MUST DO

Ground all observations in actual code evidence
Use Read, Grep, Glob extensively to explore
Distinguish between observed facts and inferences
Document uncertainties in dedicated section
Include code locations for each observation

MUST NOT DO

Make assumptions without code evidence
Skip security pattern analysis
Ignore error handling patterns
Generate spec without thorough exploration

Output Templates

Save specification as: specs/{project_name}_reverse_spec.md

Include:

Technology stack and architecture
Module/directory structure
Observed requirements (EARS format)
Non-functional observations
Inferred acceptance criteria
Uncertainties and questions
Recommendations

Knowledge Reference

Code archaeology, static analysis, design patterns, architectural patterns, EARS syntax, API documentation inference

What ships with it: 4 files

7.5 KB alongside SKILL.md