speckit-specify

Generate a SPEC_FILE and feature branch from a natural language description.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ericstiles/spec-kit-backlog --skill speckit-specify-ericstiles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/ericstiles/spec-kit-backlog/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/ericstiles/spec-kit-backlog --skill speckit-specify-ericstiles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert vague product ideas described in natural language into detailed, ready-to-implement feature specifications that align with the Spec Kit workflow, reducing ambiguity and rework.

Core Features & Use Cases

  • Generate a complete SPEC_FILE and a feature branch from a single natural language description.
  • Validate the spec against the project template and produce a quality checklist for readiness.
  • Support pre/post extension hooks and assumptions to guide planning and review.

Quick Start

Describe your feature in natural language to generate a complete spec draft and a dedicated feature branch 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 prompt into a feature specification?▼

To turn a natural language prompt into a feature specification, describe your idea to generate a complete SPEC_FILE with structured sections, measurable success criteria, and a quality checklist.

Can I generate a feature branch automatically from a text description?▼

Yes, you can generate a feature branch automatically. Applying the feature description to the Spec Kit workflow creates a dedicated branch alongside the structured specification document for planning.

How does Spec Kit validate feature specs for implementation readiness?▼

Spec Kit validates feature specs by checking them against the project template and producing a quality checklist, ensuring the specification includes clear assumptions and measurable success criteria for planning.

What is the best way to reduce ambiguity in product planning documents?▼

The best way to reduce ambiguity in product planning documents is to translate natural language ideas into detailed specifications that include potential clarifications, assumptions, and measurable success criteria.

Do I need a project template to generate a feature spec from natural language?▼

Yes, a project template is required. The system validates the generated feature spec against the project template to produce a structured document with consistent sections for planning and review.