speckit-specify

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

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

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 natural 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 into actors, actions, data, and constraints, then writes a full 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 Handling: Limits ambiguity to a maximum of 3 [NEEDS CLARIFICATION] markers and presents structured multiple-choice questions to resolve them. - Use Case: A product manager 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 Ask the agent to run /speckit-specify followed by your feature description, such as "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 /speckit-specify followed by your natural language feature description. The command generates a short name, creates a numbered directory under specs/, and writes a spec.md file with user scenarios, functional requirements, and success criteria.

How does speckit-specify handle unclear requirements?

It makes informed guesses using industry standards and documents assumptions, reserving [NEEDS CLARIFICATION] markers for critical decisions only. A maximum of 3 markers are allowed, and each is presented as a multiple-choice question for the user to resolve.

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 settings, optionally loads .specify/memory/constitution.md, and persists the feature path to .specify/feature.json.

What is the difference between timestamp and sequential feature numbering?

Sequential numbering assigns the next available 3-digit number (e.g., 003-user-auth), while timestamp numbering uses a YYYYMMDD-HHMMSS prefix. The mode is set via feature_numbering in .specify/init-options.json; sequential is the default.

Why does my spec fail the quality validation checklist?

Common failures include implementation details leaking into the spec, untestable requirements, non-measurable success criteria, or unresolved [NEEDS CLARIFICATION] markers. The command updates the spec and re-validates up to 3 iterations before reporting remaining issues.