speckit-specify

Generate a validated feature specification from a natural language feature description.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-specify-carl-fabri
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/Carl-Fabri/TestAngularSpecDriven/tree/main/test-angular/.claude/skills/speckit-specify
Command: npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-specify-carl-fabri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and error-prone. This Skill converts a plain-language feature description into a structured spec.md file with user scenarios, functional requirements, and measurable success criteria, ready for planning. ## Core Features & Use Cases - Spec Generation: Creates a numbered feature directory under specs/ with a spec.md built from the resolved spec-template, including user scenarios, requirements, and success criteria. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria, resolving up to 3 clarification questions with the user. - Extension Hooks: Executes before_specify and after_specify hooks from .specify/extensions.yml, such as automatic git branch creation. - Use Case: Describe a feature like "add OAuth2 login to the dashboard" and receive a complete, stakeholder-ready specification at specs/001-oauth2-login/spec.md with a validation checklist. ## Quick Start Ask the assistant to create a feature specification for your idea, for example: specify a feature that lets users reset their password via email.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I create a feature specification from a text description?▼

Invoke the specify command with your feature description as the argument. The Skill generates a short name, creates a numbered directory under specs/, and writes a complete spec.md with user scenarios, functional requirements, and success criteria.

What is spec-kit and how does the specify command work?▼

Spec-kit is a spec-driven development toolkit that structures features as specification documents before implementation. The specify command is the first phase, producing a validated spec.md that downstream commands like plan and tasks consume.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing templates and optionally init-options.json, memory/constitution.md, and extensions.yml. Feature specs are written under the specs/ directory by default.

How are feature directories numbered in spec-kit?▼

Numbering is controlled by feature_numbering in .specify/init-options.json. Sequential mode assigns the next three-digit number like 003, while timestamp mode uses a YYYYMMDD-HHMMSS prefix, followed by the generated short name.

What happens when the specification has unclear requirements?▼

The Skill marks critical ambiguities with up to three NEEDS CLARIFICATION markers, then presents each as a multiple-choice question with suggested answers and implications. Your responses are written back into the spec before validation completes.