speckit.specify

Generate structured feature specifications from natural language feature descriptions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and inconsistent. This Skill converts a natural language feature description into a structured spec with user scenarios, functional requirements, and measurable success criteria. ## Core Features & Use Cases - Spec Generation: Creates a full feature specification from a short description, including user scenarios, functional requirements, success criteria, and key entities. - Branch & Workspace Setup: Generates a short branch name, checks remote/local branches and feature directories for numbering, and initializes the feature workspace via a script. - Quality Validation: Produces a requirements checklist, validates the spec against it, and manages up to 3 [NEEDS CLARIFICATION] questions with structured answer options. - Use Case: A product manager types a feature idea like "add OAuth2 login" and receives a ready-to-plan specification file with acceptance criteria and a validation checklist. ## Quick Start Ask the agent to create a feature specification for your idea, for example: create a spec for adding 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 after the /speckit.specify command. The skill extracts actors, actions, data, and constraints, then writes a spec with user scenarios, functional requirements, and success criteria to the feature's spec file.

What sections does a speckit feature specification include?▼

The spec follows the template in .specify/templates/spec-template.md, covering user scenarios and testing, functional requirements, success criteria, key entities, and assumptions. Mandatory sections must be completed; irrelevant optional sections are removed.

How are clarification questions handled during spec creation?▼

At most three [NEEDS CLARIFICATION] markers are allowed, prioritized by scope, security, and user experience impact. Each question is presented with suggested answer options in a table, and the spec is updated with the user's choices.

How does the skill choose the feature branch number?▼

It checks remote branches, local branches, and existing feature directories for the highest number matching the short name, then uses N+1. If none exist, numbering starts at 1, and the create-new-feature script initializes the workspace.

What are the limitations of the generated specification?▼

The spec intentionally avoids implementation details like frameworks, languages, and APIs, focusing on what and why. Validation is capped at three iterations, and remaining issues are documented in the checklist notes if unresolved.