pre-dev-task-breakdown

Sprint task decomposition prevents oversized work items by enforcing a template that caps task duration at two weeks, requires testable acceptance criteria, and mandates a Definition of Done for each deliverable to guarantee demoable increments.

Map dependencies and risks by applying Gate 7 validation to document per-task prerequisites and potential blockers, ensuring PRD and TRD coverage, measurable success criteria, testing strategies, and team readiness before sprint planning.

Create a tasks.md file by listing one demoable deliverable per task, specifying measurable success criteria, dependencies, a testing plan, estimates under two weeks, and a strict Definition of Done to validate implementation completeness.

Yes, PRD and TRD inputs are required inputs for task breakdown, providing the high-level product requirements and technical architecture needed to generate prioritized, demoable sprint backlog items with accurate dependency mapping.

Task decomposition enforces a two-week estimate cap to prevent oversized, vague, or technical-only work items, forcing teams to deliver measurable user value through demoable working increments that validate assumptions early.