speckit-specify

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

1|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-specify-pieberrykinnie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/pieberrykinnie/hapa/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-specify-pieberrykinnie

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 - Specification Generation: Parses a feature description and writes a structured spec.md under a numbered directory in specs/ using the resolved spec-template. - Quality Validation: Creates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria, with up to 3 clarification questions presented as option tables. - Extension Hooks: Executes before_specify and after_specify hooks from .specify/extensions.yml, including optional git branch creation. - Use Case: A product manager types a feature idea like "add OAuth2 login" and receives a complete, stakeholder-ready specification with acceptance scenarios and success metrics, persisted for downstream /speckit-plan and /speckit-tasks commands. ## Quick Start Ask the agent to run /speckit-specify followed by a 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 from a text description?

Invoke /speckit-specify followed by your feature description. The skill generates a short name, creates a numbered directory under specs/, and writes a spec.md with user scenarios, functional requirements, and success criteria based on the spec-template.

What is the spec-kit specify workflow?

The specify workflow parses your feature description, creates a feature directory using sequential or timestamp numbering, writes the specification, validates it against a quality checklist, and resolves up to three clarification questions before reporting readiness for planning.

Does speckit-specify require a specific project structure?

Yes, it requires a spec-kit project with a .specify/ directory. It reads .specify/init-options.json for numbering mode, .specify/memory/constitution.md for governance, and .specify/extensions.yml for optional hooks.

How many clarification questions can a specification contain?

The skill limits specifications to a maximum of 3 NEEDS CLARIFICATION markers, prioritized by scope, security, and user experience impact. Remaining ambiguities are resolved with informed defaults documented in the Assumptions section.

Why does my spec validation keep failing?

Validation fails when the spec contains implementation details, untestable requirements, or non-measurable success criteria. The skill re-runs validation up to 3 iterations, updating the spec each time, and documents remaining issues in the checklist notes.