speckit-specify

Convert natural-language feature descriptions into structured spec.md files.

Updated Aug 23, 2025
One-click install
npx skills add https://github.com/engakhattab/DEPI_Angular_project --skill speckit-specify-engakhattab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/engakhattab/DEPI_Angular_project/tree/main/Backend/HR/.agents/skills/speckit-specify
Command: npx skills add https://github.com/engakhattab/DEPI_Angular_project --skill speckit-specify-engakhattab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert a natural-language feature idea into a clear, structured specification you can plan and build with confidence.

Core Features & Use Cases

  • Create a feature specification from a written description, ready for subsequent planning steps.
  • Optionally run pre-hooks defined in .specify/extensions.yml to support team workflows such as branching or setup.
  • Validate specification quality with an autogenerated checklist and iteration cycle, ensuring requirements are testable and free of unresolved critical gaps.

Quick Start

Describe the feature you want in one sentence after /speckit-specify and let the Skill generate the spec directory, spec.md, and requirements checklist.

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 idea into a testable specification?

To turn a natural language feature idea into a testable specification, describe your feature in a single sentence and the tool generates a structured spec.md file with user scenarios, functional requirements, and measurable success criteria.

What is the best way to validate feature requirements before implementation?

Validating feature requirements before implementation involves using an autogenerated checklist to ensure criteria are testable and free of critical gaps, iterating up to three times to refine the specification quality until resolved.

Can I define functional requirements and user scenarios from a plain text description?

Yes, you can define functional requirements and user scenarios from a plain text description by converting the natural language input into a structured feature specification complete with entities and acceptance criteria.

Does feature planning with spec validation support custom pre-hooks for team workflows?

Feature planning with spec validation supports custom pre-hooks by executing team workflow commands defined in the .specify/extensions.yml configuration file before generating the feature directory and specification template.

How many refinement iterations can I run during spec validation?

During spec validation, you can run up to three refinement iterations to resolve critical gaps and ensure all functional requirements and acceptance criteria are fully testable before saving the feature metadata.