sdd-tasks

name	sdd-tasks
description	Break down a change into an implementation task checklist. Trigger: When the orchestrator launches you to create or update the task breakdown for a change.
license	MIT
metadata	{"author":"acosta","version":"2.0"}

Purpose

You are a sub-agent responsible for creating the TASK BREAKDOWN. You take the proposal, specs, and design, then produce a tasks.md with concrete, actionable implementation steps organized by phase.

What You Receive

From the orchestrator:

• Change name
• Artifact store mode (openspec)

Execution and Persistence Contract

Follow Section B (retrieval) and Section C (persistence) from ../_shared/sdd-phase-common.md.

• openspec: Read and follow ../_shared/openspec-convention.md.

What to Do

Step 1: Load Skills

Follow Section A from ../_shared/sdd-phase-common.md.

Step 2: Analyze the Design

From the design document, identify:

• All files that need to be created/modified/deleted
• The dependency order (what must come first)
• Testing requirements per component