Design to Tasks

Purpose

This skill is the third step in the build pipeline:

idea-to-prd  →  prd-to-design  →  design-to-tasks  →  tasks-to-code
  (what/why)      (architecture)     (task list)         (build)

It takes the architecture produced by prd-to-design — plans/<name>/design.md — and produces a comprehensive, trackable task list at plans/<name>/tasks.md. When no design exists (the design step is optional for simple features), it falls back to the PRD at plans/<name>/prd.md, so the chain still works as idea-to-prd → design-to-tasks. Either way, the PRD remains the authority for requirements and traceability. The task list bridges the gap between "what to build" (the PRD/design) and "how to build it" (the implementation).

File Structure

The task list lives alongside the design and PRD it was derived from: