project-schedule-integritylisted
Install: claude install-skill vincentdania/agent-skills-for-real-work
# Project Schedule Integrity
Use when a schedule, workplan or Gantt chart must be checked before it is baselined, approved, or reported against. The output is a defect list with severities — not a summary of the schedule.
## Why schedules fail
Schedules rarely fail because tasks take longer than estimated. They fail because the dependencies are wrong, the float was never real, or the milestone dates were set by the donor before the plan existed. Check those three things first.
## Workflow
1. **Inventory the schedule.** Record: number of tasks, date range, named owners, dependency type (finish-to-start, start-to-start, finish-to-finish), lag values, and whether any resources are levelled. A schedule with no dependency column is a task list, not a schedule — say so.
2. **Check every dependency for logic errors.** Look for:
- **Hard-coded dates overriding logic** — a task with a fixed start date that contradicts its predecessor is a schedule that will not compute correctly. This is the single most common defect.
- **Circular dependencies** — task A waits on B, B waits on A.
- **Dangling tasks** — tasks with no predecessor and no successor, indicating a missed link.
- **Missing dependencies** — tasks that clearly must be sequential but are not linked.
- **Lag values with no stated reason** — lag is a modelling choice and must be justified.
3. **Recompute the critical path independently.** Do not accept the tool's output. Identify:
- The longest path by ac