speckit-specify

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

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/trungenglish/SHOPWISE --skill speckit-specify-trungenglish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/trungenglish/SHOPWISE/tree/main/.cursor/skills/speckit-specify
Command: npx skills add https://github.com/trungenglish/SHOPWISE --skill speckit-specify-trungenglish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and error-prone, often producing ambiguous requirements that derail planning. This Skill converts a natural language feature description into a structured spec.md file with user scenarios, functional requirements, and measurable success criteria. ## Core Features & Use Cases - Spec Generation: Parses a feature description, extracts actors, actions, data, and constraints, and writes a specification following the spec-kit template under a numbered specs/ directory. - Quality Validation: Creates a requirements checklist and iteratively validates the spec against completeness, testability, and technology-agnostic criteria, with up to 3 clarification questions for ambiguous points. - Extension Hooks: Supports before_specify and after_specify hooks from .specify/extensions.yml for optional git branch creation and post-processing. - Use Case: A product manager types a feature idea like "add OAuth2 login for the mobile app" and receives a ready-to-plan specification with acceptance scenarios and success metrics. ## Quick Start Ask the AI to run /speckit-specify with your feature description, for example: create a specification for adding 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 from a feature description?▼

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, functional requirements, and success criteria.

What is the spec-kit specify command used for?▼

The specify command converts a raw feature idea into a structured, technology-agnostic specification ready for planning. It focuses on what users need and why, deliberately excluding implementation details like frameworks, APIs, or code structure.

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 for feature numbering. It also reads .specify/memory/constitution.md for project principles and .specify/extensions.yml for hooks if present.

How are ambiguous requirements handled during specification?▼

Ambiguities are marked with [NEEDS CLARIFICATION] markers, limited to a maximum of 3 per spec. Each marker is presented to the user with suggested answer options and implications, then the spec is updated with the chosen answers and revalidated.

Can I customize the feature directory naming in spec-kit?▼

Yes, set SPECIFY_FEATURE_DIRECTORY explicitly to override the default. Otherwise the directory is auto-generated under specs/ using either a timestamp or sequential three-digit prefix based on the feature_numbering setting in init-options.json.