sdd-tasks

Create a dependency-ordered implementation task checklist in openspec/changes/{change-name}/tasks.md.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/dallay/opencode-docker --skill sdd-tasks-dallay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/sdd/sdd-tasks
Command: npx skills add https://github.com/dallay/opencode-docker --skill sdd-tasks-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts a change proposal, specifications, and design into a concise, dependency-ordered implementation checklist so engineers can move from design to actionable work without ambiguity.

Core Features & Use Cases

  • Structured task generation: Produces a tasks.md organized by phases with hierarchical numbering and one-line, verifiable tasks.
  • Dependency-aware ordering: Identifies file-level changes and orders tasks by dependency to ensure correct implementation sequence.
  • Compliance with project conventions: Persists the artifact into the openspec layout and enforces task sizing and verification rules for TDD or spec-driven workflows.
  • Use Case: Given a proposal and design for a new authentication flow, generate a Phase 1 foundation checklist for database and schema changes, Phase 2 implementation tasks, and Phase 3 testing tasks.

Quick Start

Create a task breakdown for the change named add-auth using the provided proposal and design and persist the tasks file to openspec/changes/add-auth/tasks.md.

Frequently Asked Questions about sdd-tasks

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

FAQPage Schema
How do I generate an implementation task checklist from design documents?▼

Task breakdown for software development works by identifying file-level changes and ordering tasks by dependency to ensure the correct implementation sequence across phases. This Skill automates that structuring process.

How do I create a dependency-ordered task list for openspec changes?▼

To create a dependency-ordered task list for openspec changes, provide your proposal and design documents. The Skill writes a structured tasks.md file into the openspec/changes/{change-name}/ directory following openspec conventions.

Do I need existing specifications and designs to generate implementation tasks?▼

Yes, existing specifications and design documents are required. The Skill applies to software development changes where a proposal, specifications, and design documents are already available in the openspec artifact layout.

What is the best way to structure implementation tasks for spec-driven workflows?▼

The best way to structure implementation tasks for spec-driven workflows is organizing them by phases with hierarchical numbering and one-line, verifiable tasks. This enforces task sizing and verification rules for TDD workflows.

Does task generation work with the openspec artifact layout?▼

Yes, task generation works exclusively with the openspec artifact layout. The Skill persists the generated checklist directly into openspec/changes/{change-name}/tasks.md, enforcing openspec conventions for task sizing and hierarchical numbering.

Why use dependency-ordered task breakdown for software implementation?▼

Use dependency-ordered task breakdown to move from design to actionable work without ambiguity. It identifies file-level changes and sequences tasks correctly so engineers implement foundational changes before dependent features.