Agent 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. Keywords: reverse engineering, code analysis, legacy, documentation, specification.

reverse-engineeringspecification-documentstechnical-writinglegacy-code
code-intelligenceID: Jeffallan/claude-skills/spec-miner

Skill Files

Browse the full folder contents for spec-miner.

Download Skill

Loading file tree…

skills/spec-miner/SKILL.md

Skill Metadata

Name
spec-miner
Description
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. Keywords: reverse engineering, code analysis, legacy, documentation, specification.

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

  1. Scope - Identify analysis boundaries (full system or specific feature)
  2. Explore - Map structure using Glob, Grep, Read tools
  3. Trace - Follow data flows and request paths
  4. Document - Write observed requirements in EARS format
  5. 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:

  1. Technology stack and architecture
  2. Module/directory structure
  3. Observed requirements (EARS format)
  4. Non-functional observations
  5. Inferred acceptance criteria
  6. Uncertainties and questions
  7. Recommendations

Knowledge Reference

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

Related Skills

  • Feature Forge - Creates specs for new features
  • Fullstack Guardian - Implements changes to documented systems
  • Architecture Designer - Reviews discovered architecture