sdd-workflow

Orchestrate a Spec-Driven Development workflow from proposal to archive.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/jorgeochipinti97/dublin-skills --skill sdd-workflow-jorgeochipinti97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-workflow
Source: https://github.com/jorgeochipinti97/dublin-skills/tree/main/skills/methodology/sdd-workflow
Command: npx skills add https://github.com/jorgeochipinti97/dublin-skills --skill sdd-workflow-jorgeochipinti97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate a formal Spec-Driven Development workflow to plan complex feature changes before coding, reducing rework and miscommunication.

Core Features & Use Cases

  • Triggers and commands to bootstrap and manage SDD phases
  • Dependency graph and artifact-store policy to coordinate work across roles
  • Standardized sub-agent launching pattern for exploration, proposal, specs, design, tasks, apply, verify, and archive
  • End-to-end traceability and archiving of changes for accountability

Quick Start

Run /sdd-init to bootstrap the SDD context and begin planning your change.

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 for planning complex feature changes?

Spec-driven development is a structured workflow that coordinates proposal, design, and verification phases before coding. It reduces rework and miscommunication by orchestrating standardized sub-agents to manage complex feature changes end-to-end.

How do I bootstrap a spec-driven development workflow?

You bootstrap the spec-driven development workflow by running the /sdd-init command. This initializes the SDD context, establishing the dependency graph and artifact-store policy required to begin structured planning for your complex feature change.

When do I need a structured workflow for feature changes?

You need a structured workflow for complex feature changes that require coordinated planning, design, and verification before coding. It ensures end-to-end traceability and accountability by archiving artifacts across all phases.

How does a sub-agent launching pattern coordinate spec-driven development phases?

The sub-agent launching pattern coordinates spec-driven development phases by standardizing exploration, proposal, specs, design, tasks, apply, verify, and archive. It applies a dependency graph and artifact-store policy to coordinate work across roles.

Can I use spec-driven development for simple code modifications?

Spec-driven development is designed for complex feature changes requiring formal planning, design, and verification. Simple code modifications do not need the standardized sub-agent launching, dependency graphs, and artifact archiving provided by this structured workflow.