sdd-tasks

Break down change proposals into phase-structured tasks.md files.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/sebasmzg/sebas.dot --skill sdd-tasks-sebasmzg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/sebasmzg/sebas.dot/tree/main/.config/opencode/skills/sdd-tasks
Command: npx skills add https://github.com/sebasmzg/sebas.dot --skill sdd-tasks-sebasmzg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down a change proposal into a concrete, executable tasks.md checklist that can be produced from proposals, specs, and design to guide implementation.

Core Features & Use Cases

  • Generate a structured tasks.md with actionable tasks organized by phase from proposals, specs, and design.
  • Provide a clear, phased plan that ensures tasks can be worked on in sequence and tracked.
  • Produce a reproducible task breakdown that can be re-used for future changes and audits.

Quick Start

Provide the change name and project context, and the skill will generate a phased, actionable 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 break down a change proposal into an actionable task checklist?

To break down a change proposal into an actionable task checklist, you provide the change name and project context to generate a structured tasks.md file organized by implementation phases.

How do I generate a phased tasks.md from project specs and design documents?

Generating a phased tasks.md from specs and design documents involves analyzing the change artifacts to produce a detailed, phase-structured task list that enforces a clear dependency sequence for implementation.

What is the best way to create a reproducible task breakdown for project management?

Creating a reproducible task breakdown for project management means transforming change artifacts into a concrete, executable checklist that can be re-used for future changes and audits.

Can I use persistence backends to store generated task lists for engineering workflows?

Yes, you can use persistence backends to store generated task lists, as the task breakdown process supports optional engram, openspec, or hybrid backends and returns a summary of the created tasks.

Do I need existing change artifacts to produce a phase-structured task list?

Yes, you need existing change artifacts such as a proposal, specs, or design documents to analyze, ensuring the resulting phase-structured task list accurately reflects the required implementation sequence.