speckit-specify

Generate a structured SPEC.md with requirements and acceptance criteria from a feature description.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/igoorstraviinsky-dev/produtos --skill speckit-specify-igoorstraviinsky-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/igoorstraviinsky-dev/produtos/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/igoorstraviinsky-dev/produtos --skill speckit-specify-igoorstraviinsky-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts natural language feature ideas into formal, structured specifications (spec.md) that include user stories, functional requirements, and acceptance criteria, accelerating planning and alignment.

Core Features & Use Cases

  • Automatic spec generation from a feature description, producing user stories, functional requirements, and acceptance criteria following a spec-driven development approach.
  • SPEC.md creation within a spec-kit project structure (.specify/), ensuring seamless integration with existing workflows.
  • Validation, branching, and quality groundwork: initializes a new branch, generates the spec file, and creates a readiness checklist for validation.
  • Use Case: When starting a new feature, provide a description after /speckit.specify to generate a ready-to-plan specification ready for planning and review.

Quick Start

Provide a feature description after /speckit.specify to generate a ready-to-plan SPEC.md and quality checklist.

Frequently Asked Questions about speckit-specify

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

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

To generate structured specifications from natural language feature descriptions, provide your text after the command to automatically produce a SPEC.md file containing user stories, functional requirements, and acceptance criteria.

What is the best way to write user stories and acceptance criteria for a new feature?

Writing user stories and acceptance criteria is best handled by converting your feature idea into a spec.md file, which structures testable requirements and explicit assumptions to accelerate planning and team alignment.

How do I create a spec.md file within a spec-kit project structure?

To create a spec.md file within a spec-kit project structure, input your feature description to initialize a new branch and generate the specification directly inside the .specify/ directory for workflow integration.

Does spec-driven development require implementation-specific details when generating requirements?

Spec-driven development does not require implementation-specific details; the generated specification remains implementation-agnostic, focusing instead on clear scope, testable functional requirements, and explicit assumptions.

Can I automatically generate a readiness checklist for feature specification validation?

Yes, you can automatically generate a readiness checklist for feature specification validation; the process creates this quality checklist alongside the spec.md file to ensure your requirements are ready for planning and review.