speckit-specify

Generate technology-agnostic feature specifications from natural language descriptions.

22|4|Updated Oct 28, 2025

Search Tags:#planning #brainstorming #specification #validation #product-management #stakeholders

Ready to run

npx skills add https://github.com/ivfarias/ceo --skill speckit-specify-ivfarias

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/ivfarias/ceo/tree/main/.gemini/skills/speckit-specify
Command: npx skills add https://github.com/ivfarias/ceo --skill speckit-specify-ivfarias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the transition from fuzzy feature ideas to precise, technology-agnostic specs that guide planning, validation, and handoffs to product, design, and engineering teams.

Core Features & Use Cases

Generates a structured spec (spec.md) and a feature branch using a clearly named format
Validates quality through a built-in checklist and handles up to 3 clarifications
Supports a brainstorm-to-spec workflow, enabling business stakeholders to approve requirements without technical detail

Quick Start

Provide a natural-language feature description to trigger the spec-writing flow and generate a ready-to-use 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 feature idea into a formal specification for stakeholder approval?▼

To turn a feature idea into a formal specification, you provide a natural-language description to generate a technology-agnostic spec. This creates a structured spec.md file with measurable success criteria, enabling business stakeholders to approve requirements without technical implementation details.

Can I generate a technology-agnostic feature specification from a brainstorming session?▼

Yes, you can generate a technology-agnostic feature specification directly from brainstorming sessions. The workflow captures natural language requirements and translates them into a structured spec.md, ensuring no implementation details are included for clean cross-functional handoffs.

How does the specification validation process handle ambiguous product requirements?▼

The specification validation process handles ambiguous product requirements by enforcing a built-in quality checklist and triggering up to 3 optional clarifications. This ensures the final specification contains measurable success criteria before handing off to development teams.

What is the best way to structure feature specifications for cross-functional product teams?▼

The best way to structure feature specifications for cross-functional teams is using a technology-agnostic format with measurable success criteria. This approach prevents premature technical decisions and allows product, design, and engineering teams to align on formal requirements.

Does this specification workflow enforce measurable success criteria for product management?▼

Yes, this specification workflow enforces measurable success criteria for product management through a structured quality-check workflow. It validates content quality by rejecting implementation details and ensuring requirements are testable before generating the final spec.

What are the limitations when creating feature specifications from natural language descriptions?▼

A key limitation when creating feature specifications from natural language descriptions is the maximum of 3 optional clarifications during the validation workflow. Additionally, the output strictly enforces technology-agnostic content, meaning no implementation details will be included in the final spec.