directory-to-spec

Generate one RFC-2119 spec file per major feature from a codebase.

5|Updated Jul 25, 2025

Search Tags:#automation #documentation #codebase #requirements #spec #feature #generate

Ready to run

npx skills add https://github.com/tomzx/agents --skill directory-to-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: directory-to-spec
Source: https://github.com/tomzx/agents/tree/main/skills/directory-to-spec
Command: npx skills add https://github.com/tomzx/agents --skill directory-to-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning a codebase's features into a set of clear specifications, enabling consistent documentation and early alignment.

Core Features & Use Cases

Discover major features from the codebase and generate a separate spec file for each feature under spec/
Ensure each specification uses RFC 2119 language for requirements and remains technology-agnostic
Provide a consistent file naming convention (lowercase, descriptive names) to simplify navigation and maintenance
Use cases include reorganizing an evolving monorepo, documenting new modules, or generating up-front specs before implementation

Quick Start

Run in the project root to generate a spec/ directory containing one specification file per major feature.

Frequently Asked Questions about directory-to-spec

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

FAQPage Schema

How do I generate feature specifications from an existing codebase?▼

To generate feature specifications from a codebase, run the automation in the project root to discover major features and output a separate spec file for each under a spec/ directory.

What is the best way to document multi-module projects with consistent requirements?▼

Generating technology-agnostic specification sets with RFC-2119 compliant requirements ensures consistent documentation across multi-module projects, providing early alignment and standardized feature descriptions for downstream tooling.

Can I use this to generate specs for a monorepo with multiple modules?▼

Yes, this automation is designed for multi-module projects like monorepos, discovering major features across the codebase and producing a consistent file naming convention to simplify navigation and maintenance.

How do I ensure my generated specification files use RFC-2119 compliant language?▼

The specification generation process automatically applies RFC-2119 compliant language to requirements, ensuring each feature spec remains technology-agnostic and suitable for downstream tooling integration.

Do I need any dependencies to create a spec directory from my source code?▼

No external dependencies are required to create a spec directory, as the automation directly analyzes the codebase in the project root to extract and generate per-feature specification files.

When should I not use automated codebase specification generation?▼

Automated codebase specification generation is not ideal for single-module projects with minimal features, as the overhead of generating a structured spec directory outweighs the documentation benefits for small codebases.