How do I install spec-miner?

Run `npx skills add https://github.com/jeffallan/claude-skills --skill spec-miner` in your terminal. You need to have run `npx skills init` once in your project first.

Which agent frameworks does spec-miner support?

spec-miner works with any agent framework supported by the Skills registry, including Claude Code, Cursor, GitHub Copilot, Cline, Codex, and Gemini CLI.

Is spec-miner free to use?

Yes. spec-miner is free to install and use. It is available from the open explainx.ai skill registry published by jeffallan.

Where can I read ratings and reviews for spec-miner?

Community ratings and review text appear on this explainx.ai skill page below the description. Reviews use a 1–5 scale and may include short written feedback from signed-in members.

Productivity

spec-miner

Reverse-engineer undocumented codebases to extract specifications, architecture, and observable behavior patterns.

jeffallan/claude-skills|Updated Jun 15, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

What it does

Uses two analytical perspectives: Arch Hat for system architecture and data flows, QA Hat for observable behaviors and edge cases
Employs systematic exploration with Glob, Grep, and Read tools to map code structure, entry points, configuration, and API routes before documentation
Documents extracted requirements in EARS format (Ubiquitous, Event-driven, State-driven, Opt

Repository

jeffallan/claude-skills

Last updated

Jun 15, 2026

Documentation

Installation Guide

Select your AI agent

How to use spec-miner on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add spec-miner

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jeffallan/claude-skills --skill spec-miner

Fetches spec-miner from jeffallan/claude-skills and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/spec-miner

Restart Cursor to activate spec-miner. Access via /spec-miner in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

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.

Trace - Follow data flows and request paths

Document - Write observed requirements in EARS format

Flag - Mark areas needing clarification

Example Exploration Patterns

# Find entry points and public interfaces Glob('**/*.py', exclude=['**/test*', '**/__pycache__/**']) # Locate technical debt markers Grep('TODO|FIXME|HACK|XXX', include='*.py') # Discover configuration and environment usage Grep('os\.environ|config\[|settings\.', include='*.py') # Map API route definitions (Flask/Django/Express examples) Grep('@app\.route|@router\.|router\.get|router\.post', include='*.py')

EARS Format Quick Reference

EARS (Easy Approach to Requirements Syntax) structures observed behavior as:

Type	Pattern	Example
Ubiquitous	The `<system>` shall `<action>`.	The API shall return JSON responses.
Event-driven	When `<trigger>`, the `<system>` shall `<action>`.	When a request lacks an auth token, the system shall return HTTP 401.
State-driven	While `<state>`, the `<system>` shall `<action>`.	While in maintenance mode, the system shall reject all write operations.
Optional	Where `<feature>` is supported, the `<system>` shall `<action>`.	Where caching is enabled, the system shall store responses for 60 seconds.

Type

Pattern

Example

Ubiquitous

The <system> shall <action>.

The API shall return JSON responses.

Event-driven

When <trigger>, the <system> shall <action>.

When a request lacks an auth token, the system shall return HTTP 401.

State-driven

While <state>, the <system> shall <action>.

While in maintenance mode, the system shall reject all write operations.

Optional

Where <feature> is supported, the <system> shall <action>.

Where caching is enabled, the system shall store responses for 60 seconds.

See references/ears-format.md for the complete EARS reference.

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

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

spec-miner

What it does

Category

Repository

Last updated

Documentation

Installation Guide

How to use spec-miner on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

List & Monetize Your Skill

Use Cases

User Story & Requirements Generation

Competitive Analysis

Roadmap Prioritization

Install Skill

Spec Miner

Role Definition

When to Use This Skill

Core Workflow

Example Exploration Patterns

EARS Format Quick Reference

Reference Guide

Constraints

MUST DO

MUST NOT DO

Output Templates

Stakeholder Communication

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

grill-me

premortem

deslop

travel-planner

framer-motion

wordpress-elementor

Reviews

Discussion