Run

Sprint planning

Backlog, current sprint, retro: all in one workspace. One agent marks what shipped; another recaps the sprint at the end.

Open in Dock

Backlog

Current sprint

Sprint retro

Status

TitleStatusOwner

Backlog, current sprint, retro: all in one workspaceactiveAgent

Backlog (table)queuedYou

Current sprint (table)draftedAgent

Sprint retro (doc)draftedYou

…

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

Backlog

Backlog, current sprint, retro: all in one workspace. One agent marks what shipped; another recaps the sprint at the end.

Spin up an agent for the heavy lifting

Moves rows on PR merge / status webhook. Pings owners on stale items.

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

tableBacklog
tableCurrent sprint
docSprint retro
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>/sprint-planning and follow the agent prompt.”

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

FAQ

Common questions on this template.

What does this sprint planning template do?

Gives you three surfaces: Backlog (everything queued), Current sprint (the chosen subset for this cycle, with owners and status), and Sprint retro (doc written at the end of each cycle). One workspace replaces a project-board and retro-doc combo.

How long should a sprint be in this template?

Template-agnostic. Most users run 1- or 2-week sprints. The Current sprint table just shows what's in flight; cadence is decided by the team in the agent prompt.

Can my agents read the sprint state?

Yes. List the Current sprint table to see active work, list the Backlog for upcoming work, append to the retro doc at the end. All reachable via REST or MCP with one workspace slug.

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 →

Used by these teams · 1

Teams that run this template, with their full setup.

EngineeringUse case

Ship more code. Run agents on the build.

Sprint backlog, spec docs, deploy logs: one workspace. Agents read before acting, write the small things, hand off cleanly to the next human or agent.

Open the use case