sdd

Name: sdd
Availability: InStock
Author: WrongStack

Create and enforce spec-driven development workflows with slash commands.

224|27|Updated May 12, 2026

Search Tags:#automation #workflow #spec-driven #spec #software-development #acceptance-criteria #task-graph

Ready to run

npx skills add https://github.com/WrongStack/WrongStack --skill sdd-wrongstack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd
Source: https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/sdd
Command: npx skills add https://github.com/WrongStack/WrongStack --skill sdd-wrongstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-Driven Development (SDD) provides a disciplined, repeatable process that ensures every non-trivial change begins with a formal spec, establishing acceptance criteria and a clear path to completion.

Core Features & Use Cases

Slash-based commands to create specs, decompose tasks, visualize dependencies, and execute work.
Enforced acceptance criteria and explicit task dependencies ensure verifiability.
Supports multiple spec templates (feature, bugfix, refactor, infra, integration, CLI) for varied workflows.
Visualizes task graphs to identify bottlenecks and supports autonomous goal loops for scalable execution.

Quick Start

Begin by creating a new spec with /sdd new and then decompose it into tasks to execute with /sdd execute.

Frequently Asked Questions about sdd

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

FAQPage Schema

What is spec-driven development and when should I use it for software projects?▼

Spec-driven development creates a disciplined workflow that turns ideas into verifiable tasks by enforcing formal specs and acceptance criteria. Use it for non-trivial software projects involving features, bug fixes, and refactors where execution tracking is essential.

How do I turn software specifications into executable tasks with dependencies?▼

Use slash-based commands to create a spec and decompose it into a task graph with dependencies. This process maps explicit task dependencies and establishes acceptance criteria to validate work execution.

Does this spec-driven workflow support templates for bug fixes and refactoring?▼

Yes, the spec-driven workflow supports multiple templates including feature, bugfix, refactor, infra, integration, and CLI. These templates adapt task decomposition and acceptance criteria validation to fit varied software development workflows.

How can I visualize task graphs to identify bottlenecks in my software development workflow?▼

Visualize task graphs by using built-in slash commands to map decomposed tasks and their dependencies. This visualization helps identify bottlenecks and supports autonomous goal loops for scalable software execution.

What's the best way to enforce acceptance criteria during task execution?▼

Adopt a spec-driven workflow that validates work against predefined metrics during execution. Using slash commands to execute tasks ensures every change is verified against the original formal spec acceptance criteria.