project-spec-extractor

Analyze a codebase and generate a SPEC.md requirements specification.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/tsilva/claudeskillz --skill project-spec-extractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-spec-extractor
Source: https://github.com/tsilva/claudeskillz/tree/main/plugins/project-spec-extractor/skills/project-spec-extractor
Command: npx skills add https://github.com/tsilva/claudeskillz --skill project-spec-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a codebase and generates a pure requirements specification (SPEC.md) that captures the project's intended behaviors and acceptance criteria.

Core Features & Use Cases

  • Discovers project identity, features, data entities, and external integrations to compose a comprehensive SPEC.md.
  • Produces a portable blueprint suitable for rebuilding or migrating a project across stacks.
  • Validates spec alignment by cross-referencing typical tests and project artifacts.

Quick Start

Provide the path to the project and, if desired, include --tech-agnostic to generate a tech-agnostic SPEC.md.

Frequently Asked Questions about project-spec-extractor

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

FAQPage Schema
How do I generate a requirements specification from an existing codebase?

To generate a requirements specification from an existing codebase, provide the project path and the tool analyzes identity, features, data, and behaviors to output a clean SPEC.md blueprint.

What is a tech-agnostic specification and when do I need one for project migration?

A tech-agnostic specification is a pure requirements blueprint excluding specific stack details, needed when you want to rebuild or migrate a project across different technologies.

Can I extract a SPEC.md blueprint for full-stack and CLI projects?

Yes, you can extract a SPEC.md blueprint for full-stack and CLI projects, as the analysis workflow adapts to API, library, and command-line project structures to document intended behaviors.

How to validate codebase behaviors against project tests and artifacts?

To validate codebase behaviors against project tests and artifacts, the specification tool cross-references tests and artifacts during its behavioral verification phase to ensure spec alignment.

What's the best way to document project features and external integrations into a blueprint?

The best way to document project features and external integrations into a blueprint is using a four-phase discovery workflow that outputs a standardized nine-section specification document.

Does the generated specification include acceptance criteria for the analyzed project?

Yes, the generated specification includes acceptance criteria, capturing the project's intended behaviors and requirements to provide a portable blueprint suitable for rebuilding or migrating the architecture.