Run

Launch tracker

Every line item from positioning to post-launch retro, owned by a human or an agent.

Open in Dock

Punch list

Launch briefs

Outreach

Status

TitleStatusOwner

Every line item from positioning to post-launch retro, owned by a human or an agentactiveAgent

Punch list (table)queuedYou

Launch briefs (doc)draftedAgent

Outreach (table)draftedYou

…

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

Every line item from positioning to post-launch retro

Every line item from positioning to post-launch retro, owned by a human or an agent.

Spin up an agent for the heavy lifting

Drafts the launch brief and post-launch retro from punch-list outcomes.

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

tablePunch list
docLaunch briefs
tableOutreach
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>/launch-tracker and follow the agent prompt.”

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

FAQ

Common questions on this template.

What is the launch tracker template for?

Coordinating a product launch end-to-end: punch list of tasks, launch briefs (pricing, copy, assets), outreach pipeline, and decision log. Replaces the typical Notion+Sheet+doc sprawl with one workspace your team and your agents both read and write.

Who should use this template?

Founder-led teams running a public launch (product, feature, marketing campaign) where 5-15 deliverables need to land in the same week. Solo founders and 2-10 person teams get the most leverage.

Can my agents drive this template?

Yes. The Punch list table and Briefs doc both accept agent writes via the Dock REST API or MCP. Common pattern: Argus drafts launch briefs, Flint pings owners on stale punch-list rows, Scout researches similar launches for reference.

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 →