speckit-specify

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

Updated Dec 12, 2024
One-click install
npx skills add https://github.com/kipariss1/czech_out_auto_bot --skill speckit-specify-kipariss1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/kipariss1/czech_out_auto_bot/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/kipariss1/czech_out_auto_bot --skill speckit-specify-kipariss1

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, ready for planning. ## 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, requirements, and success criteria. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria, with up to 3 clarification questions for ambiguous points. - Extension Hooks: Supports before_specify and after_specify hooks from .specify/extensions.yml for optional or mandatory pre/post actions such as git branch creation. - Use Case: Type a feature idea like "add OAuth2 login for the mobile app" and receive a numbered feature directory containing a validated specification and quality checklist, ready for /speckit-plan. ## Quick Start Ask the assistant to run the speckit-specify skill with a description of the feature you want to specify, for example "create a specification 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 text description?▼

Invoke the skill with your feature description as the argument. It generates a short name, creates a numbered directory under specs/, copies the spec-template, and writes a complete spec.md with scenarios, requirements, and success criteria.

What project structure does speckit-specify require?▼

It requires a spec-kit project with a .specify/ directory containing templates and optionally init-options.json, memory/constitution.md, and extensions.yml. Specs are written to a specs/ directory using sequential or timestamp numbering.

How many clarification questions can the spec contain?▼

The spec is limited to a maximum of 3 NEEDS CLARIFICATION markers. Questions are prioritized by impact: scope first, then security and privacy, then user experience, then technical details. Reasonable defaults are used for everything else.

Does speckit-specify create the git branch automatically?▼

Branch creation is optional and handled by a before_specify hook from the git extension, not by the core command. The spec directory and spec.md file are always created by the command itself, independent of branch naming.

What happens if the spec fails quality validation?▼

The skill lists failing checklist items, updates the spec to fix each issue, and re-validates up to 3 iterations. If issues remain after that, they are documented in the checklist notes and the user is warned before proceeding.