Download for MacApple silicon, macOS 14+
Skill

spec-miner

@jeffallan Updated 2026-10-30

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.

ai-agentsclaudeclaude-codeclaude-marketplaceclaude-skills

Install

With your agent

Install OMGSkills skill "jeffallan/claude-skills:spec-miner" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/Jeffallan/claude-skills /tmp/claude-skills && ln -s /tmp/claude-skills/skills/spec-miner ~/.claude/skills/spec-miner

From README

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 Scope - Identify analysis boundaries (full system or specific feature) 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.