speckit

Generate specification, plan, and task artifacts from brainstorming sessions.

22|4|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/ivfarias/ceo --skill speckit-ivfarias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit
Source: https://github.com/ivfarias/ceo/tree/main/.gemini/skills/speckit
Command: npx skills add https://github.com/ivfarias/ceo --skill speckit-ivfarias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit addresses the need to define and manage feature requirements upfront, reducing back-and-forth and misalignment across teams.

Core Features & Use Cases

  • Brainstorming-to-spec workflow that captures WHAT and WHY before implementation.
  • Generation of a complete specification, plan, and task artifacts that drive execution.
  • Supports dual implementation paths (executing plans or test-driven development) while preserving a project constitution.

Quick Start

Start a brainstorming session to capture requirements, then run speckit-specify to create the formal feature specification.

Frequently Asked Questions about speckit

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

FAQPage Schema
How do I define feature specifications before starting development?

You can generate structured artifacts including a formal specification, execution plan, and task checklists. These artifacts support both sequential execution and test-driven development paths while enforcing phase separation.

Does speckit work for test-driven development workflows?

Yes, speckit supports test-driven development by preserving a project constitution and generating structured plan and task artifacts that guide implementation through explicit checklists and standards.

What is the best way to manage project requirements and reduce back-and-forth across teams?

Managing project requirements upfront using a technology-agnostic specification workflow reduces back-and-forth. It enforces clear standards and captures requirements before building features to align design and development teams.

Can I enforce project standards and checklists during feature planning?

Yes, project standards are enforced through a constitution-driven approach that applies explicit checklists and phase separation during feature planning, ensuring technology-agnostic specs guide the implementation.

How do I transition from brainstorming feature ideas to a structured execution plan?

Transition from brainstorming to execution by running a specification workflow that transforms captured requirements into a structured plan and task artifacts, driving both sequential execution and test-driven development.