speckit-specify

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-specify-wu-mao-chia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/WU-MAO-CHIA/AI_tset_platfrom/tree/main/.opencode/skills/speckit-specify
Command: npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-specify-wu-mao-chia

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, success criteria, and a quality checklist, ready for planning. ## Core Features & Use Cases - Spec Generation: Creates a feature directory under specs/ with a spec.md based on the spec-kit template, including user scenarios, functional requirements, and measurable success criteria. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against completeness and testability criteria, with up to 3 clarification questions presented as option tables. - Extension Hooks: Supports before_specify and after_specify hooks via .specify/extensions.yml for optional git branch creation and post-processing. - Use Case: A product manager types a feature idea like "add OAuth2 login" and receives a numbered spec directory (e.g., specs/003-oauth2-login/spec.md) with validated requirements ready for /speckit-plan. ## Quick Start Run /speckit-specify followed by a description of the feature you want to specify, such as "add 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 feature description in natural language. The command generates a short name, creates a numbered directory under specs/, and writes a spec.md from the spec-kit template with requirements and success criteria.

How to write testable functional requirements for a feature spec?▼

Each requirement must be verifiable without implementation details and avoid vague language. This Skill enforces testability through a quality checklist that flags ambiguous requirements and limits clarification markers to the three most impactful questions.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing templates/spec-template.md. Specs are written to the specs/ directory, and the resolved path is persisted to .specify/feature.json for downstream commands.

Can speckit-specify create a git branch automatically?▼

Branch creation is optional and handled by a before_specify hook defined in .specify/extensions.yml, typically from a git extension. The spec directory and file are always created by the core command regardless of hooks.

What happens when a spec has unclear requirements?▼

The Skill marks critical ambiguities with up to 3 NEEDS CLARIFICATION markers, then presents each as a question with suggested answer options in a table. After you respond, it updates the spec and re-runs validation.