Recipe Post Mortem Setup
Spin up a Google Docs post-mortem, calendar review, and Chat notice in one shot after an incident without juggling three separate Workspace flows.
Overview
recipe-post-mortem-setup is an agent skill most often used in Operate (also Ship launch prep) that creates a Google Docs post-mortem, schedules a Calendar review, and notifies Chat via the `gws` recipe chain.
Install
npx skills add https://github.com/googleworkspace/cli --skill recipe-post-mortem-setupWhat is this skill?
- 3-step recipe: Docs template, Calendar insert, Chat notification via `gws` CLI
- Prerequisites: `gws` binary plus `gws-docs`, `gws-calendar`, and `gws-chat` skills
- Post-mortem body scaffold: Summary, Timeline, Root Cause, Action Items sections
- Calendar step supports attendees, start/end ISO times for review meetings
- Chat step posts to a named space (e.g. `spaces/ENG_SPACE`) with incident context
- 4-section post-mortem body scaffold (Summary, Timeline, Root Cause, Action Items)
Adoption & trust: 15.3k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
After an incident you need a doc, a review slot, and team awareness, but stitching Google Docs, Calendar, and Chat manually slows blameless follow-through.
Who is it for?
Indie SaaS or small teams standardized on Google Workspace with `gws` skills already loaded who want a copy-paste incident retro kit.
Skip if: Builders without Google Workspace, without the `gws` CLI and child skills, or who need on-call paging, severity classification, or root-cause analysis inside the agent.
When should I use this skill?
User needs to create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat after an engineering incident.
What do I get? / Deliverables
You get a templated post-mortem document, a scheduled review meeting, and a Chat announcement—ready for your team to fill in timeline and action items.
- Google Doc post-mortem with standard sections
- Calendar event for post-mortem review
- Google Chat message in target space
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Post-mortems belong on the operate/errors shelf because they close the loop after production incidents, even though the same recipe can be rehearsed during launch prep or ship readiness drills. Errors is the canonical home for incident follow-up artifacts—structured review docs, scheduled retros, and team notifications—rather than generic iteration backlog work.
Where it fits
After a production bug is fixed, run the recipe to stand up the retro doc and book the team review the same afternoon.
Before a major release, rehearse the post-mortem template so launch day has a familiar doc structure if rollback is needed.
When customer-impacting outages need a written record for support and leadership, generate the doc and notify the eng channel in one pass.
How it compares
A thin orchestration recipe over Docs/Calendar/Chat skills—not a full incident management platform or PagerDuty replacement.
Common Questions / FAQ
Who is recipe-post-mortem-setup for?
Solo builders and small platform teams using googleworkspace/cli skills who want post-incident documentation and scheduling automated from the terminal or agent.
When should I use recipe-post-mortem-setup?
Use it in Operate after an incident is mitigated to file the retro doc and meeting; you can also dry-run the flow during Ship launch readiness. Load gws-docs, gws-calendar, and gws-chat first.
Is recipe-post-mortem-setup safe to install?
Review the Security Audits panel on this Prism page before installing; the recipe runs shell commands and sends Chat messages that can expose incident details to your configured space.
Workflow Chain
Requires first: gws docs, gws calendar
SKILL.md
READMESKILL.md - Recipe Post Mortem Setup
# Set Up Post-Mortem > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-docs`, `gws-calendar`, `gws-chat` Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat. ## Steps 1. Create post-mortem doc: `gws docs +write --title 'Post-Mortem: [Incident]' --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Action Items'` 2. Schedule review meeting: `gws calendar +insert --summary 'Post-Mortem Review: [Incident]' --attendee team@company.com --start '2026-03-16T14:00:00' --end '2026-03-16T15:00:00'` 3. Notify in Chat: `gws chat +send --space spaces/ENG_SPACE --text '🔍 Post-mortem scheduled for [Incident].'`