sdd-tasks

Convert design decisions into an atomic task plan in tasks.md.

Updated Aug 27, 2026

Search Tags:#sdd #openspec #software-engineering #work-breakdown #task-planning #design-to-tasks

Ready to run

npx skills add https://github.com/fearovex/claude-config --skill sdd-tasks-fearovex

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/fearovex/claude-config/tree/main/skills/sdd-tasks
Command: npx skills add https://github.com/fearovex/claude-config --skill sdd-tasks-fearovex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down a high-level design into an atomic, ordered set of actionable tasks saved to openspec/changes/<change-name>/tasks.md for execution by sdd-apply.

Core Features & Use Cases

Atomic tasks: each item is a single, verifiable action with a concrete target.
Phase-driven planning: organizes work into logical phases that respect dependencies.
Traceability: links tasks back to the originating design and specs for audit.

Quick Start

Create a task plan for a given change by running the sdd-tasks workflow with the change name.

Frequently Asked Questions about sdd-tasks

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

FAQPage Schema

How do I convert a software design into an actionable work breakdown?▼

To convert a software design into an actionable work breakdown, you can generate an atomic, ordered task plan. This process organizes high-level design decisions into verifiable actions saved to openspec/changes/<change-name>/tasks.md for phased execution.

What is an atomic task plan in openspec-driven development?▼

An atomic task plan in openspec-driven development is an ordered set of single, verifiable actions. Each task targets a concrete file path and specifies a completion criterion, ensuring traceability back to the originating design and specs.

How do I structure task planning to respect phase dependencies?▼

You can structure task planning to respect phase dependencies by organizing work into logical phases. This approach ensures that sequential tasks respect dependency chains, creating an auditable traceability path for software engineering changes.

Can I generate verifiable tasks for openspec changes without manual file mapping?▼

Yes, you can generate verifiable tasks for openspec changes without manual file mapping. The system automatically specifies a concrete file path and a verifiable completion criterion for each task within the openspec/changes/ directory.

Does design-to-tasks planning support auditable traceability for software engineering?▼

Yes, design-to-tasks planning supports auditable traceability for software engineering. It links every generated task directly back to the originating design and specs, providing a clear audit trail within the openspec changes framework.