speckit-specify

Generate structured feature specifications from natural language descriptions using spec-kit templates.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill speckit-specify-sethdavis512
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/sethdavis512/iridium --skill speckit-specify-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and inconsistent. 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 - Specification Generation: Creates a numbered feature directory under specs/ with a spec.md file based on the spec-kit template, including user scenarios, functional requirements, and success criteria. - 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: Supports before_specify and after_specify hooks via .specify/extensions.yml for optional or mandatory pre/post actions such as git branch creation. - Use Case: A product manager types a feature idea like "add team workspaces with role-based permissions" and receives a validated, stakeholder-ready specification plus a quality checklist, ready for /speckit-plan. ## Quick Start Run /speckit-specify followed by a description of the feature you want to specify, such as "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 /speckit-specify followed by your feature description in natural language. The command generates a short name, creates a numbered directory under specs/, and writes a spec.md file with user scenarios, requirements, and success criteria based on the spec template.

What should a good feature specification include?▼

A good specification includes user scenarios with acceptance criteria, testable functional requirements, measurable technology-agnostic success criteria, and key entities. It should focus on what users need and why, avoiding implementation details like frameworks or APIs.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project structure with a .specify/ directory containing templates/spec-template.md. Specs are written to a specs/ directory, and the resolved feature path is persisted to .specify/feature.json for downstream commands.

How many clarification questions can a specification have?▼

The specification allows a maximum of 3 NEEDS CLARIFICATION markers, prioritized by 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.

What happens after the specification is created?▼

After validation passes, the command reports the feature directory, spec file path, and checklist results. You can then proceed to /speckit-clarify for further refinement or /speckit-plan to begin implementation planning.