speckit-specify

Generate feature specifications from natural language descriptions using spec-kit templates.

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-specify-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-specify-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, high-quality feature specifications from rough ideas is slow and error-prone. This Skill converts a natural language feature description into a structured, validated spec.md file following the spec-kit workflow, so planning and task breakdown can start from a solid foundation. ## Core Features & Use Cases - Specification Generation: Parses a feature description, extracts actors, actions, data, and constraints, then writes a complete spec.md from the resolved spec-template. - Quality Validation: Creates a requirements checklist and iteratively validates the spec against content quality, requirement completeness, and feature readiness criteria (up to 3 iterations). - Clarification Handling: Limits ambiguity to a maximum of 3 [NEEDS CLARIFICATION] markers and presents structured multiple-choice questions to resolve them. - Extension Hooks: Supports before_specify and after_specify hooks via .specify/extensions.yml for branch creation and post-processing. - Use Case: A product manager types a feature idea like "add passwordless email login" and receives a numbered feature directory (e.g., specs/003-passwordless-login) containing a validated spec.md ready for /speckit-plan. ## Quick Start Ask the AI to create a feature specification for your idea, for example: run speckit-specify with the description "add plant watering reminders with push notifications".

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 specify command with your feature description as the argument. The skill generates a short name, creates a numbered directory under specs/, copies the resolved spec-template, and writes a complete spec.md with scenarios, requirements, and success criteria.

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

Spec-kit is a spec-driven development toolkit that structures features as specification files before implementation. The specify command is the first phase, producing spec.md, which downstream commands like /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 principles, and .specify/extensions.yml for optional hooks.

How are ambiguous requirements handled during specification?▼

Ambiguities are marked with [NEEDS CLARIFICATION] markers, limited to a maximum of three per spec. Each marker is presented as a structured question with suggested answer options, and the spec is updated with your choices before re-validation.

Why does spec validation fail and how is it fixed?▼

Validation fails when the spec contains implementation details, untestable requirements, or non-measurable success criteria. The skill lists failing checklist items, updates the spec automatically, and re-runs validation up to three iterations.

Can I customize the feature directory naming in spec-kit?▼

Yes, set SPECIFY_FEATURE_DIRECTORY explicitly to override the default. Otherwise the directory is auto-generated under specs/ with a sequential NNN prefix or a timestamp prefix, depending on the feature_numbering option in init-options.json.