Free for 30 days on Scale.Start free
Run9 steps60 min meeting + 1-2 hr async prep, every sprint

Run a sprint planning meeting that doesn't suck

A 60-minute sprint planning meeting that ends with a written plan, a sprint goal, one owner per item, and a slack budget. The team ships what they committed in 80%+ of sprints because the commitment was honest.

Open in DockSee every step →

A 60-minute sprint planning meeting that ends with a written plan

A 60-minute sprint planning meeting that ends with a written plan, a sprint goal, one owner per item, and a slack budget. The team ships what they committed in 80%+ of sprints because the commitment was honest.

Spin up an agent for the heavy lifting

Drafts the sprint plan doc, the goal statement, and the retro template from the prior sprint's outcomes.

9 steps, 7 official links, 3 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.

5Surfaces
9Steps
3Agent prompts
7Official links
4Tools mapped
Surfaces
  • tableSteps
  • tablePointers
  • docSprint plan
  • tableCapacity log
  • 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>/run-a-sprint-planning-meeting and follow the agent prompt.”

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

Common questions on this template.

How long should sprint planning actually take?
60 minutes flat for a 2-week sprint with a 2-8 person team. 90 minutes for 3-week sprints. Anything longer is the async prep wasn't done, or the team is rebuilding the backlog in real-time. The fix is always more grooming before the meeting, not a longer meeting.
Are sprints even worth it for a small team?
For a 2-3 person team that's mostly co-located and aligned, often no - lightweight kanban (a board, daily standup, weekly review) covers the same ground without ceremony. For a 4-8 person team, especially if remote or async, sprints provide a useful commitment cadence and a natural retro rhythm. Bigger than 8 and you're past sprint-planning-as-one-meeting; you're into multi-team coordination.
What's the most common reason sprints miss?
Two: (1) capacity was overstated - the team planned for 100% of nominal capacity and reality delivered 60-70%; (2) the work was estimated without acceptance criteria, so engineers discovered scope mid-sprint. Fix capacity by reserving 20% slack and being honest about non-engineering time. Fix scope by writing acceptance criteria in grooming, not in the sprint.
Should I use story points or hours?
For a small team starting out: just use 'items' (count of issues completed). Story points add overhead that mostly pays off when you have 3+ teams comparing capacity. Hours encourage false precision. If the team is mature and wants finer granularity, Fibonacci-style story points (1, 2, 3, 5, 8) work better than hours because they explicitly encode uncertainty.
Can my AI agents help with sprint planning?
Yes. Agents are useful for: drafting the candidate sprint plan from the backlog, summarising the prior sprint's variance to feed retro, identifying stale issues for backlog grooming, drafting the sprint goal from the team's quarterly OKRs, and tracking action items between retros. The judgement calls (what to commit, what to drop, capacity, ownership) need humans. The template ships agent prompts inline for the goal-drafting and retro-prep steps.
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.

Product managementUse case

Ship a roadmap your team actually reads.

Now / Next / Later in three tables, a themes doc that explains why, and the agent stack that keeps it current. Stop maintaining a roadmap that drifts from reality.

Open the use case

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.