Spec Miner helps the agent make sense of legacy or inherited code with no documentation. It scopes the analysis, explores with Glob, Grep and Read, traces data flows and request paths, and writes observed requirements in EARS format with uncertainties flagged.
The skill works from two perspectives, an architecture view for structure and data flow and a QA view for observable behavior and edge cases, and it requires every observation to point to code evidence.
What You Get
- A five-step reverse-engineering workflow with an exploration checkpoint
- Example Glob and Grep patterns for entry points, TODO markers, configuration use and API routes
- A quick reference for EARS requirement types with examples
- A specification file saved as specs/{project_name}_reverse_spec.md
- A seven-part output: stack, structure, requirements, non-functional notes, acceptance criteria, uncertainties and recommendations
- Reference files for the analysis process, EARS format, specification template and analysis checklist
Common Use Cases
- Onboarding to an inherited project with no documentation
- Documenting an API from its route definitions
- Finding technical debt markers and undocumented business rules
- Preparing a legacy system for an enhancement or rewrite
What Makes It Unique
It restricts the agent to Read, Grep and Glob in its frontmatter, so analysis cannot change the code. It separates observed facts from inferences, requires a code location for each observation and gives uncertainties their own section, which suits a task where guessing is the main risk.
Under The Hood
The skill is a SKILL.md with four reference files that the agent loads by topic. It ships no scripts. Its frontmatter allows only the Read, Grep and Glob tools, so exploration is read-only. The one write is the final specification, which the instructions say to save under a specs folder in your project, and that file write needs the agent’s file-writing tools to be available.