speckit-specify

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

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/B18Bu/Refund-Agent --skill speckit-specify-b18bu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/B18Bu/Refund-Agent/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/B18Bu/Refund-Agent --skill speckit-specify-b18bu

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, success criteria, and a quality checklist, ready for planning. ## Core Features & Use Cases - Spec Generation: Creates a numbered feature directory under specs/ with a spec.md built from the resolved spec-template, including user scenarios, functional requirements, success criteria, and key entities. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria, with up to 3 clarification questions presented as option tables. - 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 enterprise users" and receives a complete, validated specification at specs/003-oauth2-login/spec.md ready for /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 from a text description?▼

Run /speckit-specify followed by your feature description. 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.

What is the spec-kit specify workflow for new features?▼

The workflow parses your description, extracts actors and requirements, fills the spec template sections, then validates against a requirements checklist. Up to 3 clarification questions are asked only when no reasonable default exists.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing the spec-template and optionally init-options.json, memory/constitution.md, and extensions.yml. Specs are written under the specs/ directory by default.

How are feature directories numbered in spec-kit?▼

Numbering is controlled by feature_numbering in .specify/init-options.json. Sequential mode assigns the next 3-digit number, while timestamp mode uses a YYYYMMDD-HHMMSS prefix, followed by the generated short name.

What happens when a spec has unresolved clarification markers?▼

The skill limits markers to 3 and presents each as a question with suggested answer options in a table. After you respond, it replaces the markers with your choices and re-runs validation before completion.