timeline-generator-scott-margetts

What it does

Converts a dependency-tagged task list into a visual timeline with critical path analysis. It identifies tasks that must finish on time to close the matter as planned and models delays to show downstream impacts and draft communications. It can produce filtered views for a specific workstream or jurisdiction for local counsel, and supports what-if cascade scenarios where delays trigger a cascade of downstream task moves and revised programme completion dates, along with draft client and local counsel communications.

How it works

• Mode 1 (Baseline build): build the dependency network from a matter plan, calculate ES, EF, LS, LF, and the critical path. Produce a Gantt diagram and a dependency summary. Input must include Task ID, Duration (working days), Predecessor(s), Dependency type (FS/FF/SS), and a fixed date anchor. It supports forward-scheduling or back-scheduling depending on known dates.
• Mode 2 (What-if analysis): take the existing baseline plus a proposed change, compute which tasks move, whether the critical path changes, and the new programme completion date. It also produces a draft client notification and affected local counsel communications. Input is the baseline plus the proposed change in plain language.
• Mode 3 (Baseline update): apply a confirmed change to produce a versioned updated baseline, a comparison table showing original vs revised dates for affected tasks, and trigger handoffs to other skills.
• Mode 4 (Workstream/jurisdiction view): generate a filtered Gantt and timeline for a specified workstream or jurisdiction from the full baseline. Output includes in-scope tasks, upstream constraints, downstream milestones, and ensures float is inherited from the full network calculation. It explains what is not shown and preserves the full-network float values.

When to use it

Use to establish a timing baseline, perform delay impact analyses (what-if cascades), or publish workstream-specific views for local counsel. Trigger phrases include: 'build a timeline', 'Gantt chart', 'critical path', 'what if X is delayed', 'what moves if', 'schedule impact', 'how does this affect the programme', 'when do we finish', 'can we still close on time', 'if we miss this deadline', 'run a what-if', 'visualise the plan', 'Germany timeline', 'timeline for local counsel', or requests for specific workstreams.

What it can touch

The skill uses the matter-plan-builder output to compute timelines and can produce a filtered view for a given workstream or jurisdiction. It references dependencies, durations, and fixed dates, and outputs a Gantt diagram, dependency summary, and comparison tables. It does not specify external tools beyond the stated input/output mechanisms and requires an existing baseline and, for what-if, a proposed change description.

Caveats

Inputs must be complete and include necessary dates and dependencies. If inputs are missing, the process stops and asks for the missing data. The what-if analysis can produce multiple scenarios when lags represent external determinations, and it requires explicit clarification of lag type or models as per the guidance in the baseline procedure. The approach emphasizes transparency by showing how calculations are derived for critical path tasks and any non-obvious constraints.