sdd-tasks

Convert project proposals and design documents into detailed development tasks.

1|Updated Apr 7, 2026

Search Tags:#automation #development workflow #specification #project planning #task breakdown #agile

Ready to run

npx skills add https://github.com/carlosamesar/framework-sdd --skill sdd-tasks-carlosamesar

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps teams decompose complex change proposals into clear, step-by-step tasks, facilitating better planning and execution.

Core Features & Use Cases

Task Generation: Converts proposals, specifications, and designs into detailed implementation checklists.
Workflow Support: Organizes tasks into phases for systematic development, testing, and review.
Use Case: A developer receives a new feature request and uses this Skill to produce a structured tasks.md, enabling efficient code and test development.

Quick Start

Trigger the skill with a change proposal, specifying the scope, and get back a prioritized task list ready for implementation.

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 project proposal into actionable development tasks?▼

Task breakdown converts project proposals and design documents into detailed, executable development tasks. It transforms complex change specifications into specific, testable implementation steps organized by development phase, enabling systematic planning and agile workflow coordination.

Can I generate an implementation checklist directly from a design document?▼

Yes, you can generate an implementation checklist directly from a design document by processing the specification through automated task generation. This converts proposals and designs into a structured tasks.md file, producing a prioritized, phase-organized task list ready for efficient code and test development.

What is the best way to organize feature requests for agile development workflows?▼

Organizing feature requests for agile development workflows involves grouping generated tasks into distinct development phases. Converting proposals into systematic, prioritized implementation checklists ensures tasks are specific, testable, and organized for sequential development, testing, and review cycles.

Do I need an existing specification to generate a task list?▼

Yes, you need an existing specification or change proposal to generate a task list. The task generation process requires a defined scope from a proposal or design document to produce detailed, executable implementation steps and a structured tasks.md output for your software project.

How does task breakdown by development phase improve project planning?▼

Task breakdown by development phase improves project planning by ensuring every generated task is specific, testable, and systematically ordered. Transforming design documents into structured implementation checklists facilitates execution clarity and enables efficient coordination across development, testing, and review.

Are there limitations to automating task breakdown for complex software projects?▼

A limitation of automating task breakdown is that the output quality depends entirely on the detail level of the input proposal or design document. While task generation organizes steps by phase, it cannot infer missing technical requirements or validate the feasibility of the original specification.