speckit-specify

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

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill speckit-specify-desarrolloainia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/desarrolloainia/nuevo_circuito_mir/tree/main/backend/.agents/skills/speckit-specify
Command: npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill speckit-specify-desarrolloainia

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, then validates it against a quality checklist. ## Core Features & Use Cases - Specification Generation: Parses a feature description into actors, actions, data, and constraints, then writes a full spec following the spec-kit template structure. - Quality Validation: Creates a requirements checklist and iteratively validates the spec, resolving up to 3 [NEEDS CLARIFICATION] markers through structured user questions. - Extension Hooks: Supports before_specify and after_specify hooks from .specify/extensions.yml for branch creation and post-processing automation. - Use Case: A product manager types a feature idea like "add OAuth2 login for the mobile app" and receives a numbered spec directory (e.g., specs/003-oauth2-login/spec.md) ready for planning with /speckit-plan. ## Quick Start Ask the agent to run /speckit-specify followed by a description of the feature you want to specify.

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 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. A maximum of 3 markers are allowed, each presented to the user with suggested answer options and implications.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory. It reads .specify/init-options.json for numbering configuration, .specify/memory/constitution.md for governance principles, and persists the feature path to .specify/feature.json.

Can I customize the spec directory name or git branch?▼

Yes, provide SPECIFY_FEATURE_DIRECTORY explicitly to override the auto-generated specs/NNN-short-name path. Branch naming is handled separately by the before_specify hook and can be set via GIT_BRANCH_NAME.

What happens after the specification is written?▼

The spec is validated against a quality checklist covering content quality, requirement completeness, and feature readiness. After validation and any after_specify hooks, it reports readiness for /speckit-clarify or /speckit-plan.