speckit-specify

Generate feature specifications with user stories, requirements, and acceptance criteria from natural language descriptions.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-specify-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/speckit-specify
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-specify-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, testable specification is slow and inconsistent. This Skill converts a natural language feature description into a complete spec.md following spec-driven development methodology, so planning can start from a validated document instead of scattered notes. ## Core Features & Use Cases - Automated Branch and Spec Setup: Generates a short branch name, checks remote branches, local branches, and specs directories for numbering, then runs the spec-kit create-new-feature script. - Structured Spec Generation: Produces user scenarios, functional requirements, success criteria, and key entities using the project's spec template, with at most 3 [NEEDS CLARIFICATION] markers. - Quality Validation Loop: Creates a requirements checklist, validates the spec against it, iterates up to 3 times, and presents clarification questions with suggested answers in tables. - Use Case: You type a feature idea like "add OAuth2 login for the mobile app" and receive a numbered branch, a spec.md with testable requirements and measurable success criteria, plus a checklist confirming readiness for /speckit.plan. ## Quick Start Ask the agent to create a feature specification from your description, for example: run /speckit.specify with "Add user authentication with OAuth2" to generate the branch, spec.md, and validation checklist.

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 natural language description?

Provide the feature description after the /speckit.specify command. The skill generates a short branch name, runs the spec-kit create-new-feature script, and writes a spec.md with user scenarios, functional requirements, and success criteria.

How does spec-kit numbering work for new feature branches?

The skill checks remote branches, local branches, and specs directories for the highest number matching the short-name pattern, then uses N+1. If no match exists, numbering starts at 1.

What project structure does speckit-specify require?

It requires a spec-kit project with a .specify directory containing the create-new-feature script and spec template. Without this structure, the branch creation and spec initialization steps cannot run.

How many clarification questions can a spec contain?

A maximum of 3 [NEEDS CLARIFICATION] markers are allowed, prioritized by scope, security/privacy, and user experience impact. Other gaps are filled with informed guesses documented in the Assumptions section.

Why should success criteria avoid implementation details?

Success criteria must be measurable and technology-agnostic so non-technical stakeholders can verify outcomes. Metrics like task completion time or concurrent user counts are valid; framework or database references are not.