speckit-specify

Convert natural language feature descriptions into formal specification outlines with Speckit workflow.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/duonghuan2122000/sora-piggy --skill speckit-specify-duonghuan2122000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/duonghuan2122000/sora-piggy/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/duonghuan2122000/sora-piggy --skill speckit-specify-duonghuan2122000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert a natural language feature description into a formal specification outline.

Core Features & Use Cases

  • Generate scope, requirements, success criteria, and validation artifacts from a plain-language feature description.
  • Support extension hooks and pre/post checks to ensure readiness for planning and execution.
  • Facilitate structured, reviewer-friendly specs that align with downstream planning tools.

Quick Start

Describe the feature you want to specify to begin generating a formal spec.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I convert a natural language feature description into a formal specification?

To convert a natural language description into a formal specification, input your plain-language feature details to generate a structured spec outline. This process applies the Speckit workflow to create scope, requirements, success criteria, and validation artifacts for planning.

What is the best way to generate feature requirements and success criteria from plain text?

Generating feature requirements and success criteria from plain text involves applying a structured workflow to your feature description. This creates reviewer-friendly specs complete with validation artifacts and pre/post checks to ensure planning readiness.

How do I create validation artifacts and handle extension hooks for feature planning?

Creating validation artifacts and handling extension hooks requires processing your feature description through a specification workflow. It generates formal scope and requirements while including quality checklists to support clarifications and readiness for next steps.

Can I use this to prepare structured requirements for downstream planning tools?

Yes, you can use this to prepare structured requirements for downstream planning tools. It transforms plain-language feature ideas into reviewer-friendly specs that align with planning systems and include pre/post checks.

What quality checks are applied when creating a formal specification outline?

Quality checks applied when creating a formal specification outline include pre/post checks and quality checklists. These support clarifications and ensure readiness for the next steps by validating the generated scope, requirements, and success criteria.