speckit-specify

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

Updated May 19, 2026
One-click install
npx skills add https://github.com/Nasalciuc/ATS-HERO --skill speckit-specify-nasalciuc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/Nasalciuc/ATS-HERO/tree/main/.cursor/skills/speckit-specify
Command: npx skills add https://github.com/Nasalciuc/ATS-HERO --skill speckit-specify-nasalciuc

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 file with user scenarios, functional requirements, success criteria, and a quality checklist, ready for planning. ## Core Features & Use Cases - Spec Generation: Parses a feature description, extracts actors, actions, data, and constraints, and writes a spec.md file using the project's spec template under a numbered specs/ directory. - Quality Validation: Creates a requirements checklist and iteratively validates the spec against content quality, requirement completeness, and feature readiness criteria, with up to 3 clarification questions for ambiguous points. - Extension Hooks: Supports 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 enterprise users" and receives a complete, stakeholder-ready specification with measurable success criteria and a validation checklist. ## Quick Start Ask the agent to create a feature specification from your description, for example: run /speckit-specify with the text "add user authentication with OAuth2".

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 the /speckit-specify command followed by your feature description in natural language. The skill generates a short 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 structure with a .specify/ directory containing templates and optionally init-options.json, memory/constitution.md, and extensions.yml. Specs are written to a specs/ directory by default.

Can speckit-specify create a git branch automatically?▼

Branch creation is handled by an optional before_specify hook defined in .specify/extensions.yml, typically provided by a git extension. The core command always creates the spec directory and file itself, independent of branch naming.

What happens after the specification is written?▼

The skill validates the spec against a quality checklist covering content quality, requirement completeness, and feature readiness, iterating up to 3 times on failures. It then reports the feature directory, spec file path, and readiness for /speckit-clarify or /speckit-plan.