speckit.specify

Convert natural language feature descriptions into structured specification files.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/aniruddh2003/ai-code-reviewer --skill speckit-specify-aniruddh2003
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.specify
Source: https://github.com/aniruddh2003/ai-code-reviewer/tree/main/.agent/skills/speckit.specify
Command: npx skills add https://github.com/aniruddh2003/ai-code-reviewer --skill speckit-specify-aniruddh2003

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, markdown, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill aids in converting natural language feature descriptions into comprehensive, testable, and user-focused feature specifications, streamlining the early stages of product development.

Core Features & Use Cases

  • Natural Language Processing: Converts spoken or written descriptions into structured spec files.
  • Feature Naming and Branching: Generates short, descriptive branch names and checks for existing branches.
  • Spec Writing: Provides a template for writing specs with sections for user scenarios, requirements, and success criteria.
  • Quality Validation: Ensures specifications are clear, complete, and without ambiguity.

Quick Start

Generate a feature spec using the 'specify' command with a feature description: specify "Create a new user authentication feature".

Frequently Asked Questions about speckit.specify

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

FAQPage Schema
How do I convert a natural language feature description into a structured spec?

Yes, you can use AI-powered coding to automate feature specification validation. It checks your markdown documents to ensure they are clear, complete, and free of ambiguity before project planning.

Do I need git to generate feature specifications and branch names?

Yes, you need git installed to generate feature specifications because this skill uses it for branch management. It automatically creates short descriptive branch names and checks for existing branches.

What is the best way to write testable user-focused feature specifications?

The best way to write testable user-focused feature specifications is using a structured template. This process converts natural language input into markdown documents containing distinct sections for requirements and success criteria.

Does this specification validation tool work without markdown rendering?

No, this specification validation tool requires markdown rendering to function properly. The structured feature definitions and spec files are generated and stored exclusively as markdown documents.