speckit-specify

Generates a validated feature specification from a natural language description using Spec Kit templates.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/MagnoAlves1993/handy --skill speckit-specify-magnoalves1993
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/MagnoAlves1993/handy/tree/main/.github/skills/speckit-specify
Command: npx skills add https://github.com/MagnoAlves1993/handy --skill speckit-specify-magnoalves1993

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and inconsistent. This Skill converts a natural language feature description into a structured spec.md file with user scenarios, functional requirements, and measurable success criteria, following the Spec-Driven Development workflow. ## Core Features & Use Cases - Automated Spec Generation: Creates a numbered feature directory under specs/ and writes a specification from the resolved spec-template, with at most 3 targeted clarification questions. - Quality Validation: Generates a requirements checklist and iteratively validates the spec for testability, measurability, and absence of implementation details. - Extension Hooks: Runs optional or mandatory before_specify and after_specify hooks defined in .specify/extensions.yml, such as automatic 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 criteria, ready for the planning phase. ## Quick Start Ask the assistant to run the speckit-specify skill with your feature description, 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 with Spec Kit?

Run the speckit-specify command followed by your feature description in natural language. The skill generates a short name, creates a numbered directory under specs/, and writes a spec.md file based on the resolved spec-template with user scenarios and requirements.

What is spec-driven development with GitHub Spec Kit?

Spec-driven development writes the specification before any code, using Spec Kit commands like speckit-specify, speckit-plan, and speckit-tasks. Each phase produces versioned artifacts under specs/ so requirements stay traceable from idea to implementation.

Does speckit-specify require a specific project structure?

Yes, it requires a Spec Kit project with a .specify/ directory containing templates and configuration. It optionally reads .specify/memory/constitution.md for project principles and .specify/extensions.yml for lifecycle hooks.

How many clarification questions does the specification process ask?

The skill limits clarification to a maximum of 3 NEEDS CLARIFICATION markers, prioritized by scope, security, and user experience impact. For everything else it makes informed guesses and documents assumptions in the spec.

What happens after the specification is generated?

The skill validates the spec against a quality checklist stored in checklists/requirements.md, runs any after_specify hooks, and reports the feature directory and spec file path. The spec is then ready for speckit-clarify or speckit-plan.