sdd-tasks

Name: sdd-tasks
Availability: InStock
Author: Gentleman-Programming

Translate change proposals and specs into phased tasks.md files with checkboxes.

1.3k|159|Updated Feb 16, 2026

Search Tags:#planning #requirements #tasks #openspec #software-engineering #change-management #task-breaking

Ready to run

npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-tasks-gentleman-programming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/Gentleman-Programming/agent-teams-lite/tree/main/skills/sdd-tasks
Command: npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-tasks-gentleman-programming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down a proposed change into concrete, actionable tasks suitable for implementation teams, transforming high-level ideas into a runnable plan.

Core Features & Use Cases

Generate a structured tasks.md from proposals, specs, and design artifacts.
Organize work into clearly defined phases with checkboxes and dependency ordering.
Output a ready-to-run openspec/changes/{change-name}/tasks.md for execution.

Quick Start

Create a tasks.md file for the given change, structured into named phases with concrete tasks, under openspec/changes/{change-name}/.

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 tasks?▼

Task breakdown for software projects maps dependencies, phases, and completion criteria from a change proposal into a repeatable blueprint. It organizes work into named phases with concrete tasks, checkbox tracking, and dependency ordering for execution.

What is the best way to manage dependencies and phases in a task blueprint?▼

The best way to manage dependencies and phases in a task blueprint is to generate a structured tasks.md file. This approach maps completion criteria and dependency ordering into clearly defined phases with checkboxes, creating a runnable plan for implementation teams.

How do I generate a tasks.md file for an openspec change?▼

To generate a tasks.md file for an openspec change, you apply the change proposal, specs, and design artifacts to the process. The output is a ready-to-run file placed under openspec/changes/{change-name}/tasks.md, structured into named phases with dependency ordering.

Does this task generation process work with existing design artifacts and specs?▼

Yes, the task generation process works directly with existing design artifacts and specs. It takes these high-level inputs and transforms them into a concrete, structured plan suitable for software changes and feature tweaks.

When do I need to create a structured task blueprint for software engineering changes?▼

You need to create a structured task blueprint for software engineering changes when you must transform high-level ideas into a runnable plan. This ensures implementation teams receive a concrete, actionable task list with mapped dependencies and completion criteria.