speckit-specify

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

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

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, ready for planning. ## Core Features & Use Cases - Spec Generation: Creates a feature directory under specs/ with a spec.md 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. - Extension Hooks: Runs optional or mandatory before_specify and after_specify hooks defined in .specify/extensions.yml, such as automatic git branch creation. - Use Case: Type a feature idea like "add OAuth2 login for the mobile app" and receive a numbered spec directory with a validated specification ready for /speckit-plan. ## Quick Start Ask the agent to create a feature specification by describing the feature you want, for example: specify a user notification system with email and in-app alerts.

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 text 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.

What is spec-kit and how does the specify command fit in?▼

Spec-kit is a spec-driven development workflow where features are specified before implementation. The specify command is the first step, producing spec.md, which downstream commands like /speckit-plan and /speckit-tasks consume.

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 principles, and .specify/extensions.yml for hooks.

How are clarification questions handled during specification?▼

The skill limits unclear aspects to a maximum of 3 [NEEDS CLARIFICATION] markers, prioritizing scope, security, and UX impact. Each marker is presented as a multiple-choice question with suggested answers, and the spec is updated with your selections.

Can I control the feature directory naming or git branch?▼

Yes. Provide SPECIFY_FEATURE_DIRECTORY to override the auto-generated path, or GIT_BRANCH_NAME to pass an exact branch name to the before_specify hook. Numbering mode (sequential or timestamp) is set in init-options.json.