speckit-specify

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

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-specify-andyrace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/AndyRace/heart-rate-graph/tree/main/.github/skills/speckit-specify
Command: npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-specify-andyrace

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 natural language feature description into a structured spec.md file inside a spec-kit project, complete with user scenarios, functional requirements, success criteria, and a quality checklist. ## Core Features & Use Cases - Specification Generation: Parses a feature description and writes a structured spec.md using the project's spec-template, with numbered feature directories under specs/. - Quality Validation: Creates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria, with up to 3 clarification questions. - Extension Hooks: Executes before_specify and after_specify hooks from .specify/extensions.yml, including mandatory git branch creation hooks. - Use Case: A product manager types a feature idea like "add OAuth2 login" and receives a ready-to-plan specification at specs/003-oauth2-login/spec.md with a validated quality checklist. ## Quick Start Ask the agent to run /speckit-specify followed by your feature description, for example to create a specification for adding user authentication to the app.

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?

Run /speckit-specify followed by your natural language feature description. The command generates a short feature name, creates a numbered directory under specs/, and writes a spec.md file based on the resolved spec-template.

How does speckit-specify handle unclear requirements?

It makes informed guesses using industry standards and documents assumptions, reserving [NEEDS CLARIFICATION] markers for critical decisions only. A maximum of 3 clarification questions are presented with suggested answer options before finalizing the spec.

Does speckit-specify require a specific project structure?

Yes, it requires a spec-kit project with a .specify/ directory containing templates and configuration. It reads .specify/init-options.json for feature numbering and optionally .specify/memory/constitution.md for project principles.

Can I customize the feature directory name in spec-kit?

Yes, provide SPECIFY_FEATURE_DIRECTORY explicitly to override the default. Otherwise the directory is auto-generated under specs/ using either a sequential 3-digit number or a timestamp prefix based on the feature_numbering setting.

What are before_specify and after_specify hooks?

They are extension hooks defined in .specify/extensions.yml that run before or after specification generation. Mandatory hooks execute automatically, such as git branch creation, while optional hooks are presented for manual invocation.