timeline-postmortem

Diagnoses missed deadlines via 5 Whys interviews and reschedules Google Workspace tasks with buffered timelines.

9|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/jerrylin96/dotgemini --skill timeline-postmortem-jerrylin96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: timeline-postmortem
Source: https://github.com/jerrylin96/dotgemini/tree/main/skills/timeline-postmortem
Command: npx skills add https://github.com/jerrylin96/dotgemini --skill timeline-postmortem-jerrylin96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a deadline slips, most teams just pick a new date without understanding why the original one failed, leading to repeated misses. This Skill enforces a structured root-cause retrospective before any rescheduling happens, so new timelines are grounded in diagnosis rather than optimism. ## Core Features & Use Cases - Socratic 5 Whys Interview: Guides a structured interview to classify the failure into one of four root causes: estimation failure, scope creep, blocker/dependency, or context switching. - Buffer-Based Rescheduling: Applies a root-cause-specific multiplier (1.20x to 1.50x) to remaining effort to calculate a realistic new deadline. - Pre-Mortem Risk Forecasting: Asks what could cause the new deadline to fail and establishes mitigation guards before committing. - Google Workspace Sync: Hands off updates to Google Tasks due dates, Calendar focus blocks, and appends retro reports to shared Google Docs. - Use Case: A product milestone slips by a week. The skill interviews you, identifies scope creep as the cause, applies a 1.50x buffer to remaining work, runs a pre-mortem, then updates the Google Task due date and publishes a retro report. ## Quick Start Run a postmortem on my missed milestone, diagnose the root cause, and reschedule the Google Task with an appropriate buffer.

Frequently Asked Questions about timeline-postmortem

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

FAQPage Schema
How do I run a postmortem on a missed deadline?

Invoke the skill when a task or milestone is overdue, or via the /postmortem command. It guides you through a 5 Whys interview to classify the root cause, then calculates a buffered new deadline before rescheduling.

How does the buffer multiplier for rescheduling work?

The new duration equals remaining estimated effort multiplied by a root-cause factor: 1.25x for estimation failure, 1.50x for scope creep, 1.30x for blockers, and 1.20x for context switching. This adjusts the new date based on why the original failed.

Can I update Google Tasks and Calendar after a postmortem?

Yes, the skill hands off to the google-workspace skill to update Google Task due dates and Calendar focus blocks via workspace_client.py commands. It can also append the retro report to a shared Google Doc using timeline_planner.py.

What is a pre-mortem risk forecast in project planning?

A pre-mortem asks you to imagine the new deadline was also missed and identify the top two risks that caused it. Each identified risk gets an explicit mitigation guard, and scheduling pauses if unresolved external dependencies remain.

When should I not reschedule immediately after a missed deadline?

Do not reschedule without diagnosis when the root cause is unknown or a blocker is still active. The skill requires completing the 5 Whys interview and confirming dependencies are cleared before committing to a new date.