Plan Tasks

Overview

Write a structured task breakdown for a structured change. Each task gets its own self-contained file containing everything a subagent needs — the relevant "why" from the proposal, the relevant "how" from the design, and the exact spec scenario(s) copied in verbatim.

Assume the implementing subagent is a skilled developer with zero context about this codebase, this decision history, or this feature — they won't know which files to touch, what conventions we've settled on, or why a particular approach was chosen unless you tell them. Give them everything they need — and only what they need — for their specific task. DRY. YAGNI. No line-by-line implementation instructions; describe what to build and the constraints that matter, not how to write each line.

Announce at start: "I'm using the plan-tasks skill to create the task breakdown."

1. Read Your Inputs

The following are provided:

• The change directory where all output goes (e.g. changes/<name>/)
• Completed artifact files — proposal.md, design.md, and all specs/**/*.md

Read all artifact files before proceeding. Skip any you wrote earlier in this session — you already have that context.