sdd-workflow

Guide software projects through specification, planning, and task breakdowns before code implementation.

7|2|Updated Jan 28, 2026

Search Tags:#planning #project management #development workflow #specification #requirements #sdd

Ready to run

npx skills add https://github.com/LuisSambrano/antigravity-config --skill sdd-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-workflow
Source: https://github.com/LuisSambrano/antigravity-config/tree/main/skills/1-core/sdd-workflow
Command: npx skills add https://github.com/LuisSambrano/antigravity-config --skill sdd-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of transforming vague ideas into structured, actionable specifications before writing code, ensuring clarity and alignment with project goals.

Core Features & Use Cases

Structured Specification: Guides users through a 5-step process (Constitution, Specify, Clarify, Plan, Tasks) to define project principles and feature requirements.
Reduced Ambiguity: Explicitly marks and resolves unclear requirements, preventing guesswork.
Use Case: When starting a new complex feature, use this Skill to first define the user stories, acceptance criteria, technical plan, and granular tasks, ensuring all stakeholders agree before any code is written.

Quick Start

Use the sdd-workflow skill to start planning a new feature by creating a specification document.

Frequently Asked Questions about sdd-workflow

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

FAQPage Schema

What is spec-driven development and how does it structure software projects?▼

Spec-driven development is a methodology that transforms vague ideas into structured, actionable specifications before code implementation. It uses a 5-step process—Constitution, Specify, Clarify, Plan, and Tasks—to define project principles and feature requirements, ensuring clarity and alignment with project goals.

How do I define project requirements and technical plans before writing code?▼

You define project requirements by creating a specification document through a structured 5-step workflow. This process guides you through establishing a project constitution, specifying feature requirements, clarifying ambiguities, planning technical architecture, and breaking down granular tasks before any code is written.

Can I use this workflow to reduce ambiguity in complex feature specifications?▼

Yes, the workflow explicitly marks and resolves unclear requirements during the Clarify step of the specification process. By forcing stakeholders to define user stories, acceptance criteria, and technical plans upfront, it prevents guesswork and ensures all stakeholders agree before implementation begins.

What is the best way to break down a new feature into actionable development tasks?▼

The best way to break down features is using the Tasks step within the spec-driven development workflow. After defining the project constitution, feature specifications, and technical plans, the methodology guides you through creating granular, actionable tasks to ensure structured documentation and requirement alignment.

When do I need to create a project constitution for my software development workflow?▼

You need to create a project constitution when starting a new complex feature and using spec-driven development. It is the first step of the methodology, allowing you to establish foundational project principles and ensure alignment among stakeholders before moving into feature specification and task breakdown.