Can I share this roadmap publicly?

Yes. Set workspace visibility to public; the URL becomes a shareable read-only roadmap. Comments stay private to your team.

Run

Product roadmap

Now / Next / Later in three tables, with the strategic narrative in a doc that updates as work moves.

Open in Dock

Now

Later

Themes

+1 more

TitleStatusOwner

Now / Next / Later in three tables, with the strategic narrative in a doc that updates as work movesactiveAgent

Now (table)queuedYou

Next (table)draftedAgent

Later (table)draftedYou

…

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

Now / Next / Later in three tables

Now / Next / Later in three tables, with the strategic narrative in a doc that updates as work moves.

Spin up an agent for the heavy lifting

Rewrites the themes doc when the roadmap shifts.

5 surfaces, one workspace

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

What's inside

Pre-loaded so day one is execution.

5Surfaces

Surfaces

tableNow
tableNext
tableLater
docThemes
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>/product-roadmap and follow the agent prompt.”

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

FAQ

Common questions on this template.

What's in the product roadmap template?

Four surfaces: Now (currently shipping), Next (next ~1-2 cycles), Later (queued ideas), and a Themes doc that frames the strategic narrative behind the buckets. Public-friendly: this is the workspace teams sometimes share with customers and design partners.

How is this different from Linear or Productboard?

Smaller and prose-friendly. The Themes doc carries the why; Now/Next/Later carries the what. No story-pointing, no engineering linking, no estimated-completion math. Most early-stage teams pair this with a separate execution tracker.

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