speckit-specify

Generate feature specifications from natural language descriptions with YAML parsing.

Updated May 20, 2026
One-click install
npx skills add https://github.com/Yangeok/i-cherri --skill speckit-specify-yangeok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/Yangeok/i-cherri/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/Yangeok/i-cherri --skill speckit-specify-yangeok

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the challenge of manually creating feature specifications by automating the process from natural language feature descriptions.

Core Features & Use Cases

  • Natural Language Parsing: Converts user-provided natural language into a feature specification.
  • Branch Creation: Optionally creates a git branch for the new feature.
  • Spec Directory Creation: Generates a new spec directory with a template file.

Quick Start

Use the speckit-specify command followed by a feature description, e.g., /speckit-specify "Implement a new user authentication system".

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I generate feature specifications from natural language descriptions?

Feature specifications are generated from natural language by parsing the text and creating a new spec directory with a template file in your project. This automates the manual process of writing feature requirements.

Do I need git to create spec directories for my project?

Git is required to create spec directories, as the process integrates with git-based project structures and optionally creates a git branch for the new feature. A spec-kit project setup is also required.

Can I use natural language processing to automate feature engineering tasks?

Natural language processing automates feature engineering by converting user-provided descriptions into structured specification files. Extension hooks allow for custom pre- and post-processing of the parsed text.

What's the best way to set up a spec-kit project for YAML parsing?

Setting up a spec-kit project requires ensuring YAML parsing capabilities are available and a .specify/ directory exists in your git repository. This structure allows the specification generation scripts to function correctly.

Why does my feature specification generation require a .specify directory?

Feature specification generation requires a .specify/ directory because the tool utilizes this specific path within git-based project structures to store generated spec files and templates. Without it, the directory creation fails.

speckit-specify is not working, what are the limitations of its branch creation?

Branch creation is optional and depends on a valid git environment and spec-kit project setup. Limitations include missing .specify/ directories or insufficient YAML parsing capabilities, which halt template generation.