estimate-epic-timeline

Epic timeline estimation sums all Draft Task points, applies the 1 Point = 0.5 day conversion rule, identifies parallel versus sequential work phases, and reveals the critical path. Design tasks run in parallel; Backend must complete before Frontend. Output includes total points, estimated days and weeks, task parallelization, and critical-path breakdown posted to the epic.

The Skill analyzes task dependencies and estimation points to reveal which sequential tasks form the longest timeline chain. By enforcing Backend → Frontend sequencing and recognizing parallelizable Design work, it pinpoints bottleneck phases that directly impact delivery date.

Yes. The Skill converts summed Draft Task points to estimated days and weeks using the 0.5-day-per-point rule, factoring in parallel execution windows. Result is posted as an epic comment for team visibility.

The Skill classifies Design tasks as parallelizable and enforces Backend → Frontend as mandatory sequence. This distinction isolates calendar time saved by parallel work from true sequential bottlenecks, sharpening realistic duration forecasts.

The Skill processes only Draft Tasks with estimation points. Tasks lacking points are excluded from timeline calculation, so ensure all tasks you want included carry point values before running analysis.