reverse-spec-batch

Batch reverse-engineer a codebase into architecture overview and per-module .spec.md files.

15|5|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/connor-git-yaml/reverse-spec --skill reverse-spec-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-spec-batch
Source: https://github.com/connor-git-yaml/reverse-spec/tree/main/skills/reverse-spec-batch
Command: npx skills add https://github.com/connor-git-yaml/reverse-spec --skill reverse-spec-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch reverse-engineers a codebase to generate a complete set of specifications, including an architecture overview and module-level specs, saving time and ensuring consistency across large projects.

Core Features & Use Cases

  • Generate an architecture overview index for a project.
  • Batch process modules to create per-module .spec.md files.
  • Maintain a living specs catalog by updating the index as the codebase evolves.

Quick Start

Run reverse-spec-batch on the project root to generate an architecture overview and module specs.

Frequently Asked Questions about reverse-spec-batch

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

FAQPage Schema
How do I batch generate project specs and architecture overviews from an existing codebase?

To batch generate project specs, run the tool on your project root to reverse-engineer the codebase, detect modules, and output an architecture overview index alongside per-module .spec.md files.

What is codebase reverse-engineering for spec generation and when do I need it?

Codebase reverse-engineering for spec generation analyzes your project structure to produce living specifications, needed when maintaining consistent architecture documentation across large, evolving software projects.

How do I create per-module .spec.md files for my project structure?

You create per-module .spec.md files by batch processing the codebase, which automatically detects individual modules and generates dedicated specification files recorded in a structured specs directory.

Will reverse-engineering my codebase overwrite existing module specs?

Reverse-engineering your codebase avoids duplicating existing specs unless explicitly forced, ensuring your current module specifications remain protected during batch processing.

Can I generate a living specs catalog for a large project with many modules?

Yes, you can generate a living specs catalog for large projects by creating an architecture overview index and updating it as the codebase evolves, maintaining a structured record of module progress.