speckit-specify

Convert natural language feature descriptions into structured product specifications.

Updated May 22, 2026

Search Tags:#workflow automation #requirements #feature specification #success criteria #Spec-Kit #planning readiness #YAML hooks

Ready to run

npx skills add https://github.com/brianpunzalan/webui-rubric --skill speckit-specify-brianpunzalan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/brianpunzalan/webui-rubric/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/brianpunzalan/webui-rubric --skill speckit-specify-brianpunzalan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

speckit-specify turns a natural-language feature idea into a structured, testable specification so teams can plan work without guessing requirements.

Core Features & Use Cases

Creates a complete feature spec from a user-provided description using the project’s spec template structure.
Generates testable functional requirements and measurable success criteria to support downstream planning and implementation decisions.
Uses extension hooks to automate setup and workflow integration (including pre- and post-specify hook execution when configured).

Quick Start

Describe the feature you want to specify immediately after invoking /speckit-specify in your message.

Frequently Asked Questions about speckit-specify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert natural language feature ideas into structured product specifications?▼

To convert natural language feature ideas into structured product specifications, describe the feature directly after invoking the command. The system translates the text into testable functional requirements and measurable success criteria for planning readiness.

What is the best way to generate testable functional requirements for planning readiness?▼

Generating testable functional requirements is best handled by converting feature descriptions into populated spec templates. This process ensures downstream implementation decisions are based on measurable success criteria rather than guessed requirements.

Does speckit-specify work with existing project directory structures and YAML hooks?▼

Yes, it applies to projects following the Spec-Kit directory structure, generating specs under the specs/ workspace. It natively supports optional pre- and post-processing YAML hooks to automate setup and workflow integration.

How do I validate feature specification quality and resolve missing requirements?▼

To validate feature specification quality, the system applies a checklist to the populated spec template. It automatically resolves missing requirements through up to three repair and clarification iterations before reporting readiness.

Can I generate multiple feature specifications in a single workflow run?▼

No, you cannot generate multiple feature specifications at once because the system creates exactly one feature spec per invocation. You must invoke the process separately for each feature idea to maintain structured planning readiness.