| name | incident-retrospective |
| description | Create an automation that drafts incident retrospectives. Gathers incident-channel messages from Slack, collects linked tickets and follow-ups from Linear, and publishes a retrospective draft to Notion with a timeline, impact summary, root-cause hypotheses, and action items.
|
| triggers | ["/incident-retro:setup"] |
Incident Retrospective Drafter Automation
Set up an automation that drafts incident retrospectives by pulling data from
Slack, Linear, and Notion.
Prerequisites
Required integrations
All three MCP integrations must be installed in Settings → MCP:
- Slack MCP — to gather incident-channel messages
- Linear MCP — to collect linked tickets and follow-ups
- Notion MCP — to publish the retrospective draft
Information to collect
Ask the user for:
- Incident identification — how are incidents identified? (e.g. Slack channel naming convention like
#inc-*, a Linear label, or manual trigger)
- Slack channels — which channels contain incident chatter (e.g.
#incidents, #inc-* pattern)
- Linear teams — which Linear teams/projects to inspect for follow-up tickets
- Retrospective template — what sections should the retro include? Default: Timeline, Impact, Root Cause, Action Items, Lessons Learned
- Notion destination — which Notion database or page should receive the draft
- Trigger type — manual dispatch, cron schedule, or triggered by an incident label being added
