Free for 30 days on Scale.Start free
Run6 stepsOngoing, ~1-2 hr/week + 4 hr at quarter end

Postmortem library, ongoing

A quarterly-cycling postmortem library where every incident has a consistent doc, every action item has an owner + due date + status, and every quarter ends with a themes retro the team actually uses.

Open in DockSee every step →

A quarterly-cycling postmortem library where every incident has a consistent doc

A quarterly-cycling postmortem library where every incident has a consistent doc, every action item has an owner + due date + status, and every quarter ends with a themes retro the team actually uses.

Spin up an agent for the heavy lifting

Your drafting agent (yours) writes the first-draft postmortem from incident notes you paste in, following the blameless template the workspace ships.

6 steps, 2 official links, 4 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

6Surfaces
6Steps
4Agent prompts
2Official links
4Tools mapped
Surfaces
  • tableIncidents
  • tableAction items
  • docLatest postmortem
  • tablePointers
  • docQuarter retro
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/postmortem-library and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

How is this different from `set-up-incident-response-and-postmortems`?
That template is the bootstrap: define severity levels, set up paging, write the on-call playbook, agree on the postmortem template, ship your first postmortem. This template is the operating cycle that runs *after* bootstrap: the library of every postmortem, the action items that survive across incidents, the quarterly retro that compounds the lessons. Bootstrap once, operate forever.
Why a fork at quarter-end instead of one perpetual workspace?
Postmortem libraries get heavy. By quarter 4 you have 80 incidents, 300 action items, 12 retros. The workspace gets slow and the agent's context window can't hold the whole thing. Forking quarterly bounds the working set, makes the agent fast, and gives you a clean retro horizon. Archived past quarters are read-only references.
What if our team doesn't write blameless postmortems?
Then start. The template defaults to blameless because every literature review of high-performing on-call teams (Google SRE, Atlassian, PagerDuty's State of Digital Ops) finds the same thing: blame-driven retros reduce reporting, reduce reporting reduces learning, lower learning means repeat incidents. Your agent enforces the blameless voice in the draft so the team's defaults shift over time without anyone being the bad cop.
Can I use this for security incidents too?
Yes, with one tweak. Add a column to Incidents called `customer_disclosure_required` (boolean) and a Pointers row for your team's security disclosure SLA. The agent flags rows where the column is true and reminds you about the disclosure window in the Monday rollup. The blameless template works for security incidents too.
How does the agent know what's overdue?
Action items rows have a `due` date column. The Monday rollup prompt has the agent compare `due < today` against `status=Open` and flip those rows to Overdue. If you don't set due dates, nothing gets flagged. The cycle works only if action items get real due dates at draft time.
Related templates

More from Run

RunMixed
Launch on Product Hunt the right way

12-step plan from picking the launch date to shipping the post-mortem. Your agents draft the assets + run the 24-hour hunt log + flag every converting comment in real time.

RunMixed
Launch on Hacker News (Show HN guide)

10-step plan for landing on the HN front page with a Show HN. Real title rules, real comment-thread tactics, real survival guide.

RunMixed
Automate Instagram posting with your agents

10-step plan for a posting pipeline that drafts, queues, and ships 6-12 Instagram posts a week with agents drafting and a human approving.

Browse all Run templates →

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.