skills.rest
cicero78M
cicero78MCOMMUNITY
Explore all skills by this author →
GitHub

speckit-specify

Convert natural language feature descriptions into structured specification files.

Updated Jun 8, 2025
Search Tags:#template#checklist#specification#validation#feature#speckit#nl-to-spec
One-click install
npx skills add https://github.com/cicero78M/Cicero_Web --skill speckit-specify-cicero78m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/cicero78M/Cicero_Web/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/cicero78M/Cicero_Web --skill speckit-specify-cicero78m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-specify translates a natural language feature idea into a structured, plan-ready specification, reducing ambiguity and handoff delays.

Core Features & Use Cases

  • Automates generation of a complete SPEC_FILE from a user-provided description using templates and a standardized workflow.
  • Generates a Specification Quality Checklist and supports iterative clarifications via NEEDS CLARIFICATION markers to resolve gaps.
  • Guides extension hooks before and after spec creation to extend behavior and enforce governance.

Quick Start

Describe your feature in natural language to generate a complete specification ready for review.

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 structured specification?▼

To convert a natural language feature description into a structured specification, you provide your text to generate a complete SPEC_FILE using standardized templates. This process translates your input into a ready-to-review document with a quality checklist to ensure plan-readiness.

What is the best way to reduce ambiguity when creating feature specifications for planning?▼

The best way to reduce ambiguity when creating feature specifications is to generate a SPEC_FILE with iterative NEEDS CLARIFICATION markers. These markers prompt you to resolve gaps directly, ensuring the final specification is complete and ready for planning.

How do I validate that a specification is ready for development planning?▼

To validate that a specification is ready for development planning, you use a generated Specification Quality Checklist. This checklist verifies that your natural language input has been fully translated into an actionable spec and identifies any missing requirements.

Does generating a specification from natural language require a specific project structure?▼

Generating a specification from natural language requires a spec-kit project structure with an enforced .specify directory. This structure leverages standardized templates to automate the creation of your SPEC_FILE and ensure consistent formatting.

Can I extend the specification generation workflow with custom hooks?▼

You can extend the specification generation workflow with custom hooks before and after spec creation. These extension hooks allow you to enforce governance and modify behavior around the generation of your SPEC_FILE and quality checklist.

Related Skills

Explore More Product & Management Skills→
SorinSSorinS

speckit-specify

Convert natural language descriptions into detailed software feature specifications.

Community
Advanced
jschultejschulte
3

complete-spec

Resolve [NEEDS CLARIFICATION] markers in specifications via interactive Q&A sessions.

Community
Basic
AustinZ21AustinZ21
4

speckit-implement

Execute spec-kit implementation task plans with dependency and checklist validation.

Community
Advanced
robikscuberobikscube

spec-writer

Generate CSI MasterFormat outline specifications from unstructured construction material lists.

Community
Intermediate