speckit-specify

Convert natural language feature descriptions into template-based spec files with quality checks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/luansilvadb/divi-app --skill speckit-specify-luansilvadb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/luansilvadb/divi-app/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/luansilvadb/divi-app --skill speckit-specify-luansilvadb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague, natural language feature descriptions into complete, review-ready specifications, reducing ambiguity and iteration.

Core Features & Use Cases

  • Generate a spec skeleton from a natural language description.
  • Create a dedicated spec directory under specs/ with a spec.md based on a template.
  • Run automated quality checks and produce a validation checklist for planning.

Quick Start

Enter your feature description to generate a complete, review-ready specification.

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 description into a ready spec?

To turn a natural language feature description into a ready spec, input your text to generate a dedicated feature directory under specs with a template-based spec.md file. It runs automated quality checks and produces a validation checklist for planning.

What is the best way to create a feature spec from a vague idea?

Creating a feature spec from a vague idea involves converting natural language descriptions into a complete specification template. The system reduces ambiguity by running quality-check workflows and prompting for optional clarifications to ensure review readiness.

How does automated spec validation work for feature planning?

Automated spec validation works by running a quality-check workflow against your generated feature specification. It produces a validation checklist and reports overall readiness for planning, ensuring all requirements are met before development begins.

Can I customize the feature specification template and directory structure?

Yes, you can customize the feature specification template and directory structure using integrated extension hooks. The system creates a dedicated spec directory under specs by default, but supports customization to fit your specific planning workflow.

Do I need any specific dependencies to generate a feature spec skeleton?

No specific dependencies are required to generate a feature spec skeleton. The system operates independently to convert your natural language feature descriptions into a structured spec directory with a template-based spec.md file.

When should I use a dedicated spec directory for feature requirements?

You should use a dedicated spec directory for feature requirements when you need to reduce ambiguity and iteration. It structures your natural language inputs into a review-ready specification with a validation checklist for immediate planning.