speckit-specify

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/zhangliuliuzhang/memcached-rvv-v2 --skill speckit-specify-zhangliuliuzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/zhangliuliuzhang/memcached-rvv-v2/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/zhangliuliuzhang/memcached-rvv-v2 --skill speckit-specify-zhangliuliuzhang

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 plain-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 - Spec Generation: Creates a feature directory under specs/ with a spec.md file built from the resolved spec-template, using sequential or timestamp-based numbering. - Quality Validation: Generates a requirements checklist and iterates on the spec until it passes content, completeness, and readiness checks. - Clarification Handling: Flags up to 3 critical [NEEDS CLARIFICATION] markers and presents structured multiple-choice questions to resolve them. - Use Case: A product manager types a feature idea like "add OAuth2 login for the mobile app" and receives a complete, stakeholder-ready specification with acceptance scenarios and success metrics, ready for the planning phase. ## 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/, writes spec.md from the resolved template, and validates it against a quality checklist.

How does speckit-specify handle unclear requirements?

It marks genuinely ambiguous decisions with [NEEDS CLARIFICATION] markers, limited to a maximum of three. Each marker is presented as a structured question with suggested answer options, and the spec is updated once you respond.

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 mode, .specify/memory/constitution.md for governance principles, and .specify/extensions.yml for optional hooks.

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

Yes, set feature_numbering in .specify/init-options.json to sequential for NNN-prefixed directories or timestamp for YYYYMMDD-HHMMSS prefixes. You can also explicitly provide SPECIFY_FEATURE_DIRECTORY to override auto-generation.

What happens after the specification is written?

The spec is validated against a generated requirements checklist with up to three correction iterations. After validation and any after_specify hooks complete, the spec is ready for /speckit-clarify or /speckit-plan.