speckit-specify

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-specify-eovipmak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/eovipmak/unattended-iso/tree/main/.commandcode/skills/speckit-specify
Command: npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-specify-eovipmak

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 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 it, resolving up to 3 [NEEDS CLARIFICATION] markers through structured user questions. - Extension Hooks: Runs optional or mandatory before_specify and after_specify hooks from .specify/extensions.yml, such as automatic git branch creation. - Use Case: Type a feature idea like "add OAuth2 login to the API" and receive a complete, validated specification at specs/001-oauth2-api-integration/spec.md ready for $speckit-plan. ## Quick Start Ask the agent to create a feature specification for your idea, for example: create a spec for adding user authentication with OAuth2 to the API.

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 feature description?

Invoke the specify command with your feature description as the argument. The Skill generates a short name, creates a numbered directory under specs/, writes spec.md from the resolved template, and validates it against a quality checklist.

How does spec-kit handle unclear requirements in a specification?

The Skill marks genuinely ambiguous decisions with [NEEDS CLARIFICATION] markers, limited to 3 maximum. It presents each as a multiple-choice question with suggested answers and implications, then updates the spec with your selections.

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. Specs are written to a specs/ directory by default.

Can I customize how feature directories are numbered?

Yes, set feature_numbering in .specify/init-options.json to either sequential (3-digit prefix like 003) or timestamp (YYYYMMDD-HHMMSS). You can also explicitly provide SPECIFY_FEATURE_DIRECTORY to override auto-generation.

What happens after the specification is created?

The Skill runs any after_specify extension hooks, then reports the feature directory, spec file path, and checklist results. The spec is then ready for the next phase using $speckit-clarify or $speckit-plan.