Run

Engineering retro

Replaces the post-sprint Notion page that gets lost. Carryover keeps unfinished retro actions visible.

Open in Dock

Engineering retro

Action items

Carryover

Status

TitleStatusOwner

Replaces the post-sprint Notion page that gets lostactiveAgent

Engineering retro (doc)queuedYou

Action items (table)draftedAgent

Carryover (table)draftedYou

…

Public preview of the cloned workspace. Same chrome you'll see after Open in Dock.

Replaces the post-sprint Notion page that gets lost

Replaces the post-sprint Notion page that gets lost. Carryover keeps unfinished retro actions visible.

Spin up an agent for the heavy lifting

Drafts retro from sprint board's done / cut / blocked rows + Slack threads.

4 surfaces, one workspace

Tabs, typed cells, agent presence, audit log. All live.

What's inside

Pre-loaded so day one is execution.

4Surfaces

Surfaces

docEngineering retro
tableAction items
tableCarryover
docStatus

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.

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.
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.
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>/engineering-retro and follow the agent prompt.”

Full MCP setup guide Other agent clients (Cursor, custom MCP)

FAQ

Common questions on this template.

What's the engineering retro template?

Three surfaces tuned for sprint-by-sprint engineering retros: a retro doc (one section per sprint with worked / didn't / lessons), an Action items table tracked across sprints, and a Carryover table that auto-surfaces unfinished actions from prior retros.

How does the carryover surface work?

Each retro produces 2-5 action items in the Action items table. At the start of the next retro, anything still open auto-promotes to Carryover. The honest mirror: if the same action keeps carrying over, the team needs to either delete it or change it.

Can an agent draft the retro itself?

Yes. Argus reads the sprint board's done / cut / blocked rows the night before retro, drafts a candidate retro doc, and surfaces stale Action items into Carryover. Team reads + edits in-place during the meeting.

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 →