spec-miner

Extract technical specifications and business requirements from legacy codebases.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill spec-miner-design-system-et
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-miner
Source: https://github.com/Design-System-ET/genexus-dev-opencode/tree/main/skills/spec-miner
Command: npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill spec-miner-design-system-et

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the challenge of working with undocumented or legacy codebases by systematically extracting business logic, architecture, and requirements from existing source code.

Core Features & Use Cases

  • Automated Code Archaeology: Maps dependencies, entry points, and data flows to visualize system structure.
  • Requirement Extraction: Converts observed code behavior into standardized EARS (Easy Approach to Requirements Syntax) documentation.
  • Use Case: When inheriting a complex, undocumented project, use this Skill to generate a comprehensive specification document that outlines the tech stack, API surface, and business rules, enabling faster onboarding and safer refactoring.

Quick Start

Use the spec-miner skill to analyze the current directory and generate a reverse-engineered specification document for this project.

Frequently Asked Questions about spec-miner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract business requirements from undocumented legacy code?

Extract business requirements from undocumented legacy code by systematically mapping system architecture, data flows, and functional behaviors. The analysis converts observed code logic into standardized EARS documentation for clear technical specifications.

What is the best way to reverse-engineer legacy code into specifications?

Reverse-engineer legacy code into specifications through automated code archaeology that maps dependencies, entry points, and data flows. This visualizes system structure to identify technical debt and generate comprehensive specification documents.

Can I generate onboarding documentation for an existing codebase with diverse technology stacks?

Generate onboarding documentation for an existing codebase with diverse technology stacks by mapping functional behaviors across the system. This produces comprehensive specs outlining the tech stack, API surface, and business rules.

How does code analysis map system architecture and data flows?

Code analysis maps system architecture and data flows by systematically traversing dependencies and entry points across the source code. This process visualizes the structural relationships and functional behaviors within the software.

Do I need any specific dependencies to perform code archaeology on a project directory?

No specific dependencies are required to perform code archaeology on a project directory. The analysis operates directly on the existing source code to extract technical specifications and business requirements.