speckit-specify

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

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

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 plain-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 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 iterates on the spec (up to 3 passes) until it is testable, unambiguous, and free of implementation details. - Clarification Handling: Limits open questions to 3 [NEEDS CLARIFICATION] markers and presents structured multiple-choice options for user decisions. - Use Case: A product manager types a feature idea like "add OAuth2 login" and receives a numbered feature directory (e.g., specs/003-oauth2-login/) containing a stakeholder-ready specification ready for planning. ## Quick Start Run /speckit-specify followed by a plain-language 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 a natural language description of the feature. 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 containing spec.md with user scenarios, functional requirements, success criteria, and key entities, plus a checklists/requirements.md quality checklist. It also records the feature directory in .specify/feature.json for downstream commands.

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 numbering mode, resolves the spec-template through the preset stack, and optionally loads .specify/memory/constitution.md for project principles.

How many clarification questions can a specification contain?▼

A specification is limited to a maximum of 3 [NEEDS CLARIFICATION] markers. If more exist, only the 3 most critical by scope, security, or UX impact are kept, and informed guesses are made for the rest.

Why does my spec validation keep failing?▼

Validation fails when the spec contains implementation details, untestable requirements, non-measurable success criteria, or unresolved clarification markers. The command iterates up to 3 times to fix issues, then documents remaining problems in the checklist notes.