Project Timeline
Build realistic project timelines that account for dependencies, risks, and the inevitable unexpected. Turns vague deadlines into actionable, milestone-driven plans.
Usage
Provide your project scope, team size, hard deadlines, and known constraints. The skill produces:
- Work Breakdown Structure: Project decomposed into tasks and subtasks
- Duration Estimates: Three-point estimates (optimistic, likely, pessimistic) for each task
- Dependencies: Which tasks must complete before others can start
- Critical Path: The longest chain of dependent tasks (determines project duration)
- Milestones: Key checkpoints with deliverables and dates
- Buffer Strategy: Where and how much buffer to add
- Risk Register: Threats to timeline with contingency plans
Examples
- Software Project: "Build a timeline for a web app MVP. Team: 2 developers, 1 designer. Scope: auth, dashboard, 3 core features, admin panel. Target: 8 weeks."
- Product Launch: "Timeline for launching a physical product. Steps: design finalization, manufacturing, packaging, marketing prep, distribution, PR. Launch date: 4 months."
- Office Move: "Create a timeline for relocating our 30-person office. Current lease ends in 90 days. Need to find space, sign lease, build out, move, and minimize downtime."
- Event Planning: "Build a timeline for a 200-person company conference in 6 months. Venue, speakers, sponsors, marketing, registration, logistics, and day-of coordination."
Guidelines
- Use three-point estimates and take the weighted average: (Optimistic + 4x Likely + Pessimistic) / 6
- Add 20-30% buffer to the total timeline — projects almost never finish early
- Identify the critical path first — delays there delay the entire project
- Parallelize independent tasks to compress the overall timeline
- Set milestones at natural check-in points, not arbitrary dates
- Review the timeline weekly and update with actuals — a plan is only useful if maintained
- Communicate timeline changes proactively — surprises erode trust more than delays