speckit-specify

Convert natural language feature ideas into structured spec.md files.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dantasgut/clayflow --skill speckit-specify-dantasgut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/dantasgut/clayflow/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/dantasgut/clayflow --skill speckit-specify-dantasgut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-specify automates turning a natural language feature description into a complete, planning-ready specification by applying standardized templates and checks.

Core Features & Use Cases

  • Generates a concise feature name and description
  • Creates a spec directory under specs, populates it with the feature template, and writes spec.md
  • Validates quality with a built-in checklist and handles clarifications (up to 3) when details are ambiguous
  • Supports extension hooks for pre-action and post-action customization

Quick Start

Describe a feature you want to specify to generate a complete spec ready for planning.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I turn a natural language feature idea into a structured specification?▼

To generate a feature specification from natural language, you provide a feature description and the system automatically creates a structured spec directory under specs, populates a spec.md file, and applies standardized templates.

What is the best way to automate feature spec generation for product planning?▼

Automating feature spec generation involves using standardized templates and a built-in validation checklist to transform text descriptions into planning-ready specifications, ensuring completeness while handling up to three clarifications for ambiguous input.

How does the specification validation checklist handle ambiguous feature descriptions?▼

The specification validation checklist ensures clarity by limiting clarifications to three items when user input is ambiguous, enforcing a quality-check process that confirms completeness before finalizing the spec.md file.

Can I customize the feature specification workflow with pre-action and post-action hooks?▼

Yes, the feature specification workflow supports extension hooks for pre-action and post-action customization, allowing you to integrate automated outline generation and validation into your existing planning processes.

What files and directories are created when generating a feature spec?▼

Generating a feature spec creates a spec directory under the specs path, populates it with the feature template, and writes the final structured specification details into a spec.md file alongside a validation checklist.