speckit-specify

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

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

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 - 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, resolving up to 3 [NEEDS CLARIFICATION] markers through structured user questions. - Extension Hooks: Executes before_specify and after_specify hooks from .specify/extensions.yml, including mandatory git branch creation hooks. - Use Case: A product manager types a feature idea like "add OAuth2 login" and receives a complete, stakeholder-ready specification at specs/003-oauth2-login/spec.md, ready for /speckit-plan. ## Quick Start 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/, writes spec.md from the resolved template, and validates it against a quality checklist.

What does the speckit-specify command generate?▼

It generates a feature directory (e.g., specs/003-user-auth) containing spec.md with user scenarios, functional requirements, success criteria, and key entities, plus a checklists/requirements.md quality checklist. It also records the path in .specify/feature.json.

Does speckit-specify require a spec-kit project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory. It reads .specify/init-options.json for feature numbering, .specify/memory/constitution.md for governance principles, and .specify/extensions.yml for hooks.

How are [NEEDS CLARIFICATION] markers handled in the spec?▼

The spec allows a maximum of 3 [NEEDS CLARIFICATION] markers for decisions that significantly impact scope, security, or user experience. Each marker is presented to the user as a structured question with suggested answer options, then replaced with the chosen answer.

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

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