speckit-specify

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

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

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 following the spec-kit template, with quality validation built in. ## Core Features & Use Cases - Spec Generation: Creates a numbered feature directory under specs/ with a spec.md file containing user scenarios, functional requirements, success criteria, and key entities. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against it, resolving issues and managing up to 3 [NEEDS CLARIFICATION] markers through structured user questions. - Extension Hooks: Runs optional and mandatory before_specify/after_specify hooks defined in .specify/extensions.yml, such as automatic git branch creation. - Use Case: A maintainer receives a feature request issue and runs the command with the description; the Skill produces specs/003-user-auth/spec.md, persists the path to .specify/feature.json, and reports readiness for /speckit-plan. ## Quick Start Ask the agent to run /speckit-specify followed by a description of the feature you want specified, such as adding OAuth2 login to your application.

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/, copies the spec-template to spec.md, and fills in user scenarios, requirements, and success criteria.

How does speckit-specify handle unclear requirements?▼

It makes informed guesses using industry defaults and documents them in an Assumptions section. Only critical ambiguities become [NEEDS CLARIFICATION] markers, capped at 3, which are presented as multiple-choice questions for the user to resolve.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing the template resolution stack. It optionally reads .specify/memory/constitution.md for governance constraints and .specify/extensions.yml for hooks.

How are spec directories numbered in spec-kit?▼

Numbering is configured in .specify/init-options.json via feature_numbering. Sequential mode assigns the next 3-digit number like 003-user-auth, while timestamp mode uses a YYYYMMDD-HHMMSS prefix.

What happens after the specification is written?▼

The spec is validated against a generated quality checklist at checklists/requirements.md, with up to 3 fix iterations. After validation and any after_specify hooks, it reports the feature directory and readiness for /speckit-clarify or /speckit-plan.