speckit.specify

Translate natural language feature descriptions into testable feature specifications.

Updated Oct 4, 2025
One-click install
npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-specify-peancharoen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.specify
Source: https://github.com/peancharoen/lcbp3/tree/main/.agents/skills/speckit.specify
Command: npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-specify-peancharoen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates vague feature ideas into precise, plan-ready specifications that can be reviewed, tested, and planned for development.

Core Features & Use Cases

  • Extracts actors, actions, data, and constraints from a natural language feature description.
  • Generates structured specification artifacts including user scenarios, functional requirements, and success criteria.
  • Manages assumptions and clarifications to ensure a clearly scoped feature.

Quick Start

Provide a natural-language feature description to generate a complete, testable feature specification.

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 natural language feature description into a testable specification?

To turn a natural language feature description into a testable specification, provide your text to the Skill. It analyzes the input to extract actors, actions, data, and constraints, then generates structured functional requirements, user scenarios, and success criteria.

What is the best way to define feature requirements when my initial idea is vague?

The best way to define feature requirements from a vague idea is to process the text through automated requirement analysis. It identifies missing information, fills gaps with informed assumptions, and asks clarifying questions to ensure a clearly scoped, testable feature.

How do I generate user scenarios and success criteria from an unstructured feature idea?

You generate user scenarios and success criteria by inputting your unstructured feature idea. The system parses the natural language to identify core components and automatically produces structured specification artifacts including risk assessments and technology-agnostic functional requirements.

Can I create technology-agnostic functional requirements without writing them manually?

Yes, you can create technology-agnostic functional requirements automatically. The Skill translates natural language descriptions into a complete specification, ensuring all requirements and constraints are defined in a format independent of specific implementation technologies.

How does requirement validation work when translating ideas into feature specifications?

Requirement validation works by analyzing the natural language input for actors and constraints, then managing assumptions and clarifications. It highlights gaps in the feature description, asking targeted questions to validate scope before generating the final specification.

Do I need a structured format to start generating a feature specification?

No, you do not need a structured format to start generating a feature specification. You simply provide a natural-language feature description, and the system extracts the necessary actors, actions, and data to build a complete, plan-ready specification.