speckit-specify

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

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/PanyaPrimal/selfHandlerApp --skill speckit-specify-panyaprimal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/PanyaPrimal/selfHandlerApp/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/PanyaPrimal/selfHandlerApp --skill speckit-specify-panyaprimal

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 numbered feature directory under specs/ with a spec.md built from the resolved spec-template, covering user scenarios, requirements, success criteria, and key entities. - Quality Validation: Generates a requirements checklist and iterates on the spec until it passes content-quality and completeness checks, with up to 3 clarification questions presented as option tables. - Extension Hooks: Runs optional or mandatory before_specify and after_specify hooks from .specify/extensions.yml, such as automatic git branch creation. - Use Case: Type a feature idea like "add OAuth2 login" and receive a validated, stakeholder-readable specification at specs/003-oauth2-login/spec.md, ready for $speckit-plan. ## Quick Start Ask the agent to create a feature specification for your idea, for example: create a spec for adding team workspaces with role-based permissions.

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 plain text description?

Invoke the specify command with your feature description as the argument. The skill 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 is spec-kit and how does the specify command fit in?

Spec-kit is a specification-driven development workflow using a .specify project structure. The specify command is the first phase, producing spec.md, which downstream commands like plan and tasks consume to generate implementation plans and task lists.

Does speckit-specify require a specific project structure?

Yes, it requires a spec-kit initialized project with a .specify/ directory containing templates and optionally init-options.json, memory/constitution.md, and extensions.yml. Feature directories are created under specs/ by default.

How are clarification questions handled during spec generation?

The skill limits NEEDS CLARIFICATION markers to a maximum of three, prioritized by scope, security, and UX impact. Each question is presented with suggested answer options in a table, and the spec is updated with your choices before re-validation.

Can I customize the feature directory naming or numbering?

Yes, set SPECIFY_FEATURE_DIRECTORY explicitly to override the default. Otherwise numbering comes from .specify/init-options.json: sequential three-digit prefixes or timestamp prefixes based on the feature_numbering setting.