speckit-specify

Generate a feature specification from a natural language description in a Spec Kit project.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-specify-damian-garces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/damian-garces/spec-driven-development/tree/main/spec-driven-project/.claude/skills/speckit-specify
Command: npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-specify-damian-garces

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, testable feature specifications from rough ideas is slow and inconsistent. This Skill turns a plain-language feature description into a structured spec.md file following the Spec Kit methodology, complete with user scenarios, functional requirements, and measurable success criteria. ## Core Features & Use Cases - Specification Generation: Creates a numbered feature directory under specs/ with a spec.md built from the resolved spec-template, capturing actors, actions, data, and constraints. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against completeness, testability, and technology-agnostic criteria, with up to 3 clarification questions presented as option tables. - Extension Hooks: Executes optional and mandatory before_specify and after_specify hooks defined in .specify/extensions.yml, such as automatic git branch creation. - Use Case: A product manager types a feature idea like "add OAuth2 login for the mobile app" and receives a validated, stakeholder-ready specification ready for the planning phase. ## Quick Start Ask the agent to create a feature specification for your idea, for example by describing the feature you want after invoking the specify command.

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 with Spec Kit?

Invoke the specify command with a natural language description of your feature. The skill generates a short name, creates a numbered directory under specs/, and writes a spec.md from the resolved spec-template with scenarios, requirements, and success criteria.

What is spec-driven development and when should I use it?

Spec-driven development is a workflow where a validated specification is written before any code, so planning and tasks derive from agreed requirements. Use it when features need stakeholder alignment, testable requirements, and measurable outcomes before implementation.

Does speckit-specify require a specific project structure?

Yes, it requires a Spec Kit project with a .specify/ directory containing templates and configuration such as init-options.json. It also reads .specify/memory/constitution.md for project principles and persists the feature path to .specify/feature.json.

How are clarification questions handled during specification?

The skill limits open questions to a maximum of 3 NEEDS CLARIFICATION markers, prioritizing scope, security, and user experience impact. Each question is presented with suggested answer options in a table, and the spec is updated with your choices.

Why does the spec validation checklist keep failing?

Validation fails when the spec contains implementation details, untestable requirements, or non-measurable success criteria. The skill iterates up to 3 times to fix issues automatically, then documents remaining problems in the checklist notes.

Can I customize branch creation and hooks in Spec Kit?

Yes, define hooks under hooks.before_specify and hooks.after_specify in .specify/extensions.yml. Hooks can be optional or mandatory, and a git extension hook can create the feature branch while the spec directory is always created by the core command.