speckit-specify

Generate feature specifications from natural language descriptions using spec-kit templates.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-specify-msaid1976
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/msaid1976/TSP-SmartAIRoute/tree/main/SmartRouteAI/.agents/skills/speckit-specify
Command: npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-specify-msaid1976

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, high-quality feature specifications from rough ideas is slow and error-prone. This Skill turns a natural language feature description into a structured, validated specification document with branch creation, quality checklists, and clarification handling. ## Core Features & Use Cases - Automated Spec Generation: Parses a feature description, extracts actors, actions, data, and constraints, then writes a complete spec.md following the spec-kit template. - Branch and File Scaffolding: Generates a short branch name and runs the create-new-feature script to set up the feature branch and spec file automatically. - Quality Validation Loop: Creates a requirements checklist, validates the spec against it, and iterates up to three times to resolve issues. - Clarification Management: Limits open questions to three [NEEDS CLARIFICATION] markers and presents structured option tables for user decisions. - Use Case: A product manager types a feature idea like "add OAuth2 login" and receives a ready-to-plan specification with user scenarios, functional requirements, and measurable success criteria. ## Quick Start Ask the AI to create a feature specification for your idea, for example: run speckit-specify with the description "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 from a feature description?▼

Provide the feature description as input and the skill generates a short branch name, runs the create-new-feature script, and writes a complete spec.md from the spec-kit template. It then validates the result against a quality checklist before reporting readiness for planning.

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

Spec-kit is a specification-driven development workflow using a .specify directory with templates and scripts. The specify command converts a natural language feature description into a structured spec with user scenarios, requirements, and success criteria.

Does speckit-specify require an existing project structure?▼

Yes, it requires a spec-kit project structure with a .specify directory containing templates and the create-new-feature script. It also reads optional files like init-options.json for branch numbering mode and extensions.yml for hooks.

How many clarification questions can a specification contain?▼

A specification is limited to a maximum of three [NEEDS CLARIFICATION] markers. The skill prioritizes clarifications by impact: scope first, then security and privacy, then user experience, and makes informed guesses for everything else.

What happens if the specification fails quality validation?▼

The skill lists failing checklist items with specific issues, updates the spec to address each one, and re-runs validation up to three iterations. If issues remain after three attempts, it documents them in the checklist notes and warns the user.