sdd-tasks

Break down change proposals into phased implementation tasks with dependencies.

Updated Apr 1, 2026

Search Tags:#automation #planning #documentation #engineering #sdd #task-breakdown

Ready to run

npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-tasks-maxculen86

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/maxculen86/coding-bro-ai/tree/main/internal/assets/skills/sdd-tasks
Command: npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-tasks-maxculen86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down a change into an implementation task checklist that can be handed to engineers or automation.

Core Features & Use Cases

Automatically convert proposals, specs, and design documents into a structured tasks.md.
Organize tasks by phase with clear acceptance criteria and dependencies.
Integrate with Engram/openspec workflows to persist or share the task plan.

Quick Start

Provide a change proposal and let the agent generate a ready-to-apply 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 software change proposal into actionable engineering tasks?▼

To break down a software change proposal, provide the proposal, spec, and design documents to generate a structured tasks.md file. The output organizes implementation tasks by phase with concrete, testable steps and clear dependencies for engineers.

Can I automatically generate a task checklist from design documents?▼

Yes, you can automatically generate a task checklist from design documents. The system analyzes your specs and proposals to produce an organized tasks.md file or an in-memory task structure, depending on your selected persistence mode.

What is the best way to organize implementation tasks by phase with clear dependencies?▼

Organizing implementation tasks by phase is handled automatically by analyzing your proposal and design documents. The generated task breakdown structures each phase with clear acceptance criteria and explicit dependencies for seamless execution.

Do I need a tasks.md file to integrate task breakdowns into my engineering workflow?▼

You do not strictly need a tasks.md file, as the breakdown can be persisted as an in-memory task structure. However, generating a tasks.md file allows you to directly share and integrate the actionable task plan within engineering workflows.

Does this task breakdown approach work with Engram and openspec workflows?▼

Yes, the task breakdown integrates directly with Engram and openspec workflows. This integration allows you to persist and share the generated implementation task plan seamlessly across your existing engineering automation pipeline.

Why are my manually created implementation tasks missing clear acceptance criteria?▼

Manual implementation tasks often lack clear acceptance criteria because they are not systematically derived from specs. Automatically generating the breakdown from design documents ensures every task includes concrete, testable steps and explicit dependencies.