speckit-specify

Generate structured feature specifications from natural-language descriptions.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-specify-alienstro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/alienstro/mediapipe-scroll/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-specify-alienstro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-specify turns a natural-language feature idea into a complete, ready-to-plan specification, reducing back-and-forth and keeping requirements clear and testable.

Core Features & Use Cases

  • Creates/updates a feature specification from a user-provided description, including scenarios, functional requirements, and measurable success criteria.
  • Respects project structure and optional extension hooks (before/after specify) to integrate with existing workflows.
  • Validates specification quality via an automatically generated checklist and iterates up to three times to reach readiness.

Quick Start

Type /speckit.specify followed by your feature description to generate a new spec directory and spec.md ready for planning.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I generate a feature specification from a natural language description?

To generate a feature specification from a natural language description, input your feature idea to automatically create a spec directory and spec.md file containing scenarios, functional requirements, and success criteria.

Can I use git hooks to automate feature spec generation in my workflow?

You can use git hooks and optional pre/post extension hooks to automate branching and integrate feature spec generation seamlessly into your existing project workflows.

How does quality validation work for generated feature specs?

Quality validation for generated feature specs works by applying an automatically generated checklist to evaluate readiness, iterating up to three times until the specification meets quality standards.

What is the best way to structure feature specifications for downstream planning?

The best way to structure feature specifications for downstream planning is to use a dedicated specs/ directory structure, ensuring requirements remain clear, testable, and ready for the next workflow phase.

Do I need any specific dependencies to create feature specs from text?

You do not need any specific dependencies to create feature specs from text, as the generation process operates independently without requiring external components or libraries.

What is included in the completion report after generating a feature spec?

The completion report after generating a feature spec includes the file paths for the created spec directory and spec.md, confirming the mandatory generation steps and quality validation are finished.