estimate-epic-timeline

Name: estimate-epic-timeline
Availability: InStock
Author: Semicolon

Sum Draft Task points to estimate epic timelines and identify critical paths.

Updated Dec 11, 2025

Search Tags:#timeline #estimation #epic #critical-path #points

Ready to run

npx skills add https://github.com/semicolon-devteam/semo --skill estimate-epic-timeline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: estimate-epic-timeline
Source: https://github.com/semicolon-devteam/semo/tree/main/packages/biz/discovery/skills/estimate-epic-timeline
Command: npx skills add https://github.com/semicolon-devteam/semo --skill estimate-epic-timeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

모든 Draft Tasks의 포인트를 합산해 에픽 전체 일정과 병렬/순차 여부를 예측합니다.

Core Features & Use Cases

총 포인트, 예상 일수/주, 병렬/순차 목록, 크리티컬 경로 제공
에픽 코멘트로 일정 인사이트 공유

Quick Start

에픽의 포인트를 기반으로 일정 정보를 코멘트로 추가합니다.

Frequently Asked Questions about estimate-epic-timeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I estimate an epic timeline from task points?▼

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.

What's the best way to identify the critical path in my project schedule?▼

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.

Can I use task points to calculate how many weeks an epic will take?▼

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.

How do I determine which tasks can run in parallel versus sequentially?▼

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.

What happens if Draft Tasks don't have estimations?▼

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.