Build

Feature flag library

Flag hygiene. Cleanup queue forces removal instead of accumulation. Decision log captures why each flag existed.

Open in Dock

Flags

Cleanup queue

Flag decisions

Status

TitleStatusOwner

Flag hygieneactiveAgent

Flags (table)queuedYou

Cleanup queue (table)draftedAgent

Flag decisions (doc)draftedYou

…

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

Flag hygiene

Flag hygiene. Cleanup queue forces removal instead of accumulation. Decision log captures why each flag existed.

Spin up an agent for the heavy lifting

Flags entries past their cleanup-by date into the cleanup queue.

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

tableFlags
tableCleanup queue
docFlag decisions
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>/feature-flag-library 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 feature flag library template?

A Flags table (flag name, status, scope, owner, created date), a Cleanup queue table (flags older than 90 days awaiting removal), and a Flag decisions doc that captures the why behind each flag (rollout plan, rollback criteria).

Why track feature flags in Dock instead of LaunchDarkly?

Dock isn't the flag runtime — it's the audit and decisions layer alongside it. LaunchDarkly (or Statsig, etc.) holds the actual flag state; Dock holds the human reasoning, the cleanup commitments, and the post-rollout review.

Can an agent help clean up stale flags?

Yes. A weekly cron-style agent: read the Flags table, find any with status=on for 90+ days, append to Cleanup queue with the original owner. Owner removes the flag in production, marks the row done.

Related templates

More from Build

BuildMixed

Launch your iPhone app on the App Store

10-step plan from 'I have a build on my Mac' to 'users are downloading from search.' Real Apple gates, real gotchas, real agent prompts.

BuildMixed

Build a webapp in a day

10-step plan from blank idea to deployed app with auth, a database, and a domain — all in 24 hours. Battle-tested defaults so you don't waste 6 hours picking a stack.

BuildMixed

Launch your Android app on Google Play

10-step plan from 'I have an APK on my laptop' to 'users are installing from Play search.' Real Google gates, real gotchas, real agent prompts.

Browse all Build templates →