speckit-spec-driven-development

Guide users from initial concepts to executable tasks through structured spec-driven workflows.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/javierhbr/random-poc --skill speckit-spec-driven-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-spec-driven-development
Source: https://github.com/javierhbr/random-poc/tree/main/custom-skills/sdd/speckit-codex-skill
Command: npx skills add https://github.com/javierhbr/random-poc --skill speckit-spec-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of transforming abstract product ideas into concrete, actionable specifications, plans, and executable tasks, ensuring clarity and reducing ambiguity before implementation.

Core Features & Use Cases

  • Spec-Driven Development: Guides users through defining requirements, clarifying ambiguity, and creating technical plans.
  • Workflow Automation: Provides a structured playbook for both greenfield and brownfield development.
  • Use Case: When starting a new feature, use this skill to first define the "what" and "why" in a clear specification, then generate a technical plan, and finally break it down into small, manageable tasks for the development team.

Quick Start

Use the speckit skill to create a constitution for a new project.

Frequently Asked Questions about speckit-spec-driven-development

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

FAQPage Schema
How do I turn abstract product ideas into executable development tasks?

Spec-driven development transforms abstract product ideas into executable tasks by guiding you through defining requirements, clarifying ambiguity, creating technical plans, and generating actionable development tasks.

What is a project constitution in spec-driven development?

A project constitution defines the foundational operating rules for your project. It serves as a base layer in the 3-layer context model to govern workflows and reference materials before writing specifications.

How do I plan technical implementations for new software features?

You can plan technical implementations by first writing a clear specification defining the "what" and "why", then generating a technical plan, and finally breaking it down into manageable tasks.

Can I use this workflow automation for both new and existing projects?

Yes, this workflow automation provides a structured playbook supporting both greenfield development for new projects and brownfield development for existing codebases to streamline requirement planning.

What is the best way to reduce ambiguity before starting software implementation?

The best way to reduce ambiguity before implementation is to use a structured spec-driven workflow that clarifies requirements and establishes a clear technical plan before generating executable tasks.

How does the 3-layer context model work for requirements management?

The 3-layer context model structures project knowledge by separating operating rules, workflows, and deep reference materials to ensure clarity and reduce ambiguity during task generation.