Back to catalog
Human reviewedDevelopment

Skill dossier

spec-miner

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A read-only reverse-engineering skill that explores an undocumented codebase and writes an EARS-format specification grounded in code evidence.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Scopes the analysis and maps structure using Glob, Grep and Read.
  • Traces data flows and request paths through the code.
  • Writes observed requirements in EARS format with code locations.
  • Flags uncertainties and saves a specification to specs/{project_name}_reverse_spec.md.

Limitations & scope

  • Can only describe what the code shows; intent and business rules remain inferences.
  • Restricted to Read, Grep and Glob, so it cannot run the system to confirm behavior.
  • Quality of output was not verified on a real legacy project.

Relevant for

  • Engineers onboarding to inherited code
  • Teams documenting legacy systems
  • Planners scoping enhancements

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
5
Markdown files
5
scripts
0
references
4
Size
12.1 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/spec-miner/references/analysis-checklist.mdReference2 KB
skills/spec-miner/references/analysis-process.mdReference1.3 KB
skills/spec-miner/references/ears-format.mdReference1.8 KB
skills/spec-miner/references/specification-template.mdReference2.4 KB
skills/spec-miner/SKILL.mdInstruction4.7 KB

SKILL.md frontmatter

{
  "name": "spec-miner",
  "description": "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.",
  "license": "MIT",
  "allowed-tools": "Read Grep Glob",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "workflow",
    "triggers": "reverse engineer, legacy code, code analysis, undocumented, understand codebase, existing system",
    "role": "specialist",
    "scope": "review",
    "output-format": "document",
    "related-skills": "feature-forge, fullstack-guardian, architecture-designer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Scope the analysis

    Identify boundaries: full system or a specific feature.

  2. 02
    Action

    Explore and trace

    Map structure with Glob, Grep and Read, then follow data flows and request paths.

  3. 03
    Decision

    Check coverage

    Confirm sufficient file coverage; if key entry points remain unread, keep exploring before documenting.

  4. 04
    Output

    Write specification

    Save the spec with stack, structure, EARS requirements, uncertainties and recommendations.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

10 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

4 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

The skill is limited to Read, Grep and Glob, but the saved spec may expose sensitive config or business logic, so check before sharing.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/spec-miner # .claude/skills/spec-miner
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/spec-miner/SKILL.md.
  2. Review the license, prerequisites and all bundled resources.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Check that SKILL.md for spec-miner is discoverable at the destination, then ask Claude Code to use it on a small test task.

Prerequisites

  • Can only describe what the code shows; intent and business rules remain inferences.
  • Restricted to Read, Grep and Glob, so it cannot run the system to confirm behavior.
  • Quality of output was not verified on a real legacy project.

Example prompts

Representative task

Use the spec-miner skill on the billing module in this repository. Map entry points and data flows, write observed requirements in EARS format with file locations, and list open questions separately.

Inspect before use

Read the spec-miner skill files at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/spec-miner/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Requires separating observed facts from inferences.
  • Read-only tool allowlist limits side effects.

Considerations

  • Large codebases may exceed what exploration covers.
  • Writes a spec file into the repo's specs directory.
Research conclusion

A careful, low-risk way to document undocumented systems, as long as its inferences are reviewed.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/spec-miner
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.