plan-tasks

Break down software changes by synthesizing approved proposal, design, and specification artifacts into self-contained, isolated task files. This structured task breakdown ensures each implementation unit includes all necessary context, acceptance criteria, and completion conditions with no cross-task dependencies.

Avoid over-splitting by enforcing intelligent task grouping that merges related work into meaningful delivery units. Instead of creating standalone infrastructure tasks, it groups API, persistence, and logic components together to prevent overlapping work and merge conflicts.

Create self-contained task files by decomposing specification artifacts into independently executable, reviewable task units. Each file provides autonomous subagents with all necessary context, acceptance criteria, and completion conditions required to execute without cross-task dependencies.

Yes, approved proposal, design, and specification artifacts are required inputs. The task planning process synthesizes these engineering workflow artifacts to decompose changes into structured, executable task lists with proper context and acceptance criteria.

Unstructured task breakdown causes merge conflicts when poorly scoped or overlapping implementation tasks lead to wasted developer time. Without intelligent task grouping, fragmented work creates cross-task dependencies that delay feature delivery and increase integration friction.