speckit-specify

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

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill speckit-specify-karentenorio963
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/KarenTenorio963/curso-mcp-karentenorio/tree/main/entregas/s4/mi-proyecto-speckit/.agents/skills/speckit-specify
Command: npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill speckit-specify-karentenorio963

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 to extract actors, actions, data, and constraints, then writes a complete spec following the spec-kit template. - Quality Validation: Creates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria (up to 3 iterations). - Clarification Management: Limits ambiguity by asking at most 3 prioritized [NEEDS CLARIFICATION] questions with suggested answer options. - Use Case: A product owner types a feature idea like "add OAuth2 login for the mobile app" and receives a numbered feature directory (e.g., specs/003-oauth2-login) containing a validated spec.md and quality checklist, ready for /speckit-plan. ## Quick Start Run /speckit-specify followed by your feature description to generate a validated feature specification in the specs directory.

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?▼

Run /speckit-specify followed by your feature description. The skill extracts actors, actions, data, and constraints, then writes a complete spec.md with user scenarios, functional requirements, and success criteria into a numbered directory under specs/.

What is spec-kit and how does the specify command fit in?▼

Spec-kit is a specification-driven development workflow from GitHub. The specify command is the first phase: it produces a validated spec.md that downstream commands like /speckit-clarify, /speckit-plan, and /speckit-tasks consume.

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 feature numbering, .specify/memory/constitution.md for governance constraints, and persists the feature path to .specify/feature.json.

How many clarification questions does the specification process ask?▼

At most 3 [NEEDS CLARIFICATION] markers are allowed per specification. Questions are prioritized by impact: scope first, then security/privacy, then user experience, then technical details. Reasonable defaults are used for everything else.

Why does spec validation fail after generating a specification?▼

Validation fails when the spec contains implementation details, untestable requirements, non-measurable success criteria, or unresolved clarification markers. The skill updates the spec and re-validates up to 3 iterations before warning the user.