skills.rest
d0whc3r
d0whc3rCOMMUNITY
Explore all skills by this author →
GitHub

speckit-specify

Convert natural-language feature descriptions into structured, testable specifications.

2|Updated Feb 16, 2026
Search Tags:#requirements#acceptance criteria#feature specification#product planning#spec validation#user scenarios#hook-driven workflow
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-specify-d0whc3r
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.trae/skills/speckit-specify
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-specify-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the guesswork in translating a natural-language feature idea into a structured, testable specification that stakeholders can review and plan against.

Core Features & Use Cases

  • Creates an actionable feature spec from a plain-language description, including user scenarios, functional requirements, and measurable success criteria.
  • Validates specification quality by generating a checklist, running validation against it, and iterating on fixes until the spec meets the defined quality bar.
  • Supports workflow extensibility via optional pre- and post-spec hooks configured in .specify/extensions.yml to align with repository-specific branching or automation.

Quick Start

Ask the system to create a new feature specification by providing your feature description after the /speckit.specify command 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 turn a feature idea into a testable specification?▼

A testable specification includes user scenarios, functional requirements, and measurable success criteria. This skill generates these structured elements from a plain-language description to validate quality and support planning.

What is the best way to write acceptance criteria from a plain language description?▼

The best way to write acceptance criteria from a plain language description is to generate a structured spec that validates quality via a checklist and iterates on fixes until requirements meet the defined quality bar.

How do I validate feature specification quality before planning?▼

To validate feature specification quality, generate a checklist and run validation against it, iterating on fixes until the spec meets the defined quality bar.

Can I run custom automation hooks during product planning spec generation?▼

You can run custom automation hooks during product planning spec generation by configuring optional pre- and post-spec hooks in a repository extensions file to align with branching or automation needs.

Does the feature specification tool resolve directory placement automatically?▼

The feature specification tool resolves spec directory placement automatically by determining the correct location based on project options or provided overrides during generation.

How do I create user scenarios for new product features?▼

To create user scenarios for new product features, provide a natural-language description and the system converts it into a structured specification including detailed user scenarios for stakeholder review.

Related Skills

Explore More Product & Management Skills→
tellbomtellbom

speckit-specify

Convert natural language feature descriptions into structured specifications with acceptance criteria.

Community
Advanced
iltan987iltan987

speckit-specify

Generate formal feature specifications from natural language descriptions.

Community
Advanced
alienstroalienstro

speckit-specify

Generate structured feature specifications from natural-language descriptions.

Community
Advanced
Lozovoi-RodionLozovoi-Rodion
12

clickup-feature-creator

Generate ClickUp EPIC and Feature tickets from product ideas.

Community
Advanced