sdd-tasks

Break down a change into a phase-based implementation task checklist.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/adacosdev/dotfiles --skill sdd-tasks-adacosdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/adacosdev/dotfiles/tree/main/dot_config/opencode/skills/sdd-tasks
Command: npx skills add https://github.com/adacosdev/dotfiles --skill sdd-tasks-adacosdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down a change into an implementation task checklist. When orchestrating changes, this skill helps produce a concrete plan that can be followed and tracked.

Core Features & Use Cases

  • Generates a phase-based task breakdown (Phase 1–Phase 4) with concrete actions and acceptance criteria.
  • Supports persistence strategies (Engram / OpenSpec / Hybrid) and clear artifact naming.
  • Useful for change requests, design proposals, and release kickoffs to align teams and schedules.

Quick Start

Provide the Change Name and project context to generate a full tasks.md with Phase 1-4 steps.

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 software change request into an implementation task checklist?

To break down a change request, generate a phase-based task checklist covering Phase 1 through Phase 4 with concrete actions, acceptance criteria, and standardized formatting for project orchestration.

What is phase-based task planning for software change management?

Phase-based task planning structures software changes into sequential phases with stepwise actions and acceptance criteria. It enforces standardized formatting to guide change-initiated work and produce trackable artifacts.

How do I generate a tasks.md artifact for a release kickoff?

Generate a tasks.md artifact by providing the change name and project context. The skill outputs a full phase-based task breakdown document to align teams and schedules for release kickoffs.

Does task generation support different persistence strategies for workflow documentation?

Task generation supports Engram, OpenSpec, and Hybrid persistence strategies. These modes enforce stepwise planning rules, persistence guidelines, and clear artifact naming for the generated task checklists.

Can I use this task breakdown approach for design proposals and change requests?

Yes, you can use this task breakdown approach for change requests and design proposals. It translates proposed changes into concrete, trackable plans that align teams and schedules across software projects.

What are the limitations of automated task generation for software changes?

Automated task generation requires clear project context and a defined change name to function. It focuses strictly on producing phase-based task checklists and does not execute the implementation work itself.