sdd (Spec Driven Development)

Enforce a spec-driven development workflow with templates and traceability.

Updated Aug 27, 2026

Search Tags:#design #templates #spec-driven #requirements #QA #traceability #guidelines

Ready to run

npx skills add https://github.com/ragnarula/cc-plugins --skill sdd-spec-driven-development

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd (Spec Driven Development)
Source: https://github.com/ragnarula/cc-plugins/tree/main/sdd/skills/sdd
Command: npx skills add https://github.com/ragnarula/cc-plugins --skill sdd-spec-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The sdd skill codifies a non-negotiable spec-driven workflow for software projects, ensuring teams consistently produce and align requirements, designs, tasks, tests, and implementations.

Core Features & Use Cases

Enforces structured artifact creation (FR/NFR specs, design docs, task breakdowns)
Provides templates and project guidelines to maintain consistency across teams
Enables end-to-end traceability from requirements to code for better validation

Quick Start

Start by reviewing the project guidelines and templates, then create a feature folder with specification.md, design.md, and a tasks plan aligned to the workflow. Use this to guide iterative refinement and implementation.

Frequently Asked Questions about sdd (Spec Driven Development)

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

FAQPage Schema

How do I implement spec-driven development to ensure traceability from requirements to code?▼

Spec-driven development standardizes your workflow by requiring structured artifacts—functional and non-functional specs, design docs, and task breakdowns—aligned end-to-end. This creates traceable requirements linked to implementation, enabling validation and consistency across teams.

What templates and guidelines do I need to set up a spec-driven project?▼

The sdd skill provides project templates and guidelines including specification.md, design.md, and task planning documents. Start by reviewing these templates, then create a feature folder structure that enforces consistent artifact creation and alignment with your workflow.

Can spec-driven development improve QA and requirements validation?▼

Yes. Spec-driven development enables end-to-end traceability, allowing QA teams to validate implementations against documented requirements and design decisions. This reduces gaps between specs and code and strengthens validation rigor.

How do I maintain consistency across multiple teams using spec-driven workflows?▼

The sdd skill prescribes standardized templates, project guidelines, and architecture decision frameworks that teams follow uniformly. Enforcing this non-negotiable workflow across projects ensures all teams produce aligned requirements, designs, and implementations.

What's the difference between spec-driven development and ad-hoc requirements gathering?▼

Spec-driven development enforces structured artifact creation, formal design review, and documented traceability, whereas ad-hoc gathering often lacks consistency and validation checkpoints. Spec-driven approaches reduce rework and improve team alignment through disciplined documentation.