generate-spec

Generate specification files from requirements into specs/[feature-name]/spec.md.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/teliha/dev-workflows --skill generate-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-spec
Source: https://github.com/teliha/dev-workflows/tree/main/skills/generate-spec
Command: npx skills add https://github.com/teliha/dev-workflows --skill generate-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the chaos of unstructured requirements by automatically generating comprehensive, well-organized specification documents.

Core Features & Use Cases

  • Requirements to Specs: Convert bullet points, user stories, or conversations into detailed technical specifications.
  • Precision Control: Adjust detail level from quick overview to thorough implementation guide.
  • Context Integration: Use existing documentation as background for consistent spec generation.

Quick Start

generate spec from: ユーザー認証機能が欲しい generate spec -p 30 from: 簡単な TODO アプリ generate spec --precision 100 from: [detailed requirements]

Frequently Asked Questions about generate-spec

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

FAQPage Schema
How do I convert requirements and user stories into a technical specification?

Generate a specification by providing your requirements, ideas, or user stories as input. The Skill transforms unstructured text into a comprehensive, well-organized specification document and outputs it to specs/[feature-name]/spec.md, automatically applying consistent structure and detail.

Can I use existing documentation to guide how my spec is generated?

Yes. Provide context files alongside your requirements, and the Skill ingests them to ensure your generated specification aligns with existing conventions, structure, and documentation patterns in your project.

How do I control the level of detail in a generated specification?

Use the --precision flag to adjust detail level. Lower values (e.g., -p 30) produce quick overviews; higher values (e.g., --precision 100) generate thorough implementation guides tailored to your needs.

What input formats work with specification generation?

Specification generation accepts bullet points, user stories, conversational notes, and structured requirements as input. The Skill processes any unstructured or semi-structured text describing features, requirements, or ideas.

When should I generate a specification instead of writing one manually?

Generate a specification when you have requirements, ideas, or discussions that are unstructured or scattered across documents. Automatic generation eliminates formatting inconsistency, ensures comprehensive coverage, and produces output faster than manual documentation.

Does specification generation work with multilingual requirements?

Yes. The Skill processes requirements written in multiple languages, including Japanese, and generates structured specification documents that maintain consistency regardless of input language.