pre-dev-task-breakdown

Task breakdown decomposes features into working software increments, each delivering measurable user value within 2 weeks. Define each task with a specific deliverable, success criteria, dependencies, and effort estimate to ensure nothing ships incomplete.

A valuable task delivers both user value and technical progress, not just technical activity. Each task must include testable success criteria, a clear deliverable, and mapping to user-facing outcomes so teams validate work incrementally.

Task sizing follows S/M/L/XL guidelines with a hard maximum of 2 weeks effort per task. Oversized tasks create integration risk and delay validation; smaller increments enable frequent delivery and early feedback.

Document task dependencies explicitly to unblock parallel work, and define a testing strategy upfront so acceptance criteria are clear before development begins. Include risk mitigations and a Definition of Done to prevent incomplete handoffs.

Task breakdown applies after the dependency map is approved, during pre-development planning and gate 7 validation. Use it to convert feature maps, API design, and data models into concrete, value-driven work items across PRD/TRD gates.