How to set up Notion’s Ship OS to run your product development cycle

AI is changing how software gets built, and agents are becoming an extension of the product team. They draft PRDs, write code, and move work forward in minutes instead of days. As agents take on more of the work, the opportunity shifts to designing a system that keeps the entire product development cycle connected. Without that shared context, even the fastest workflows start to fragment.

Ship OS is that system. It's a ready-to-use Notion setup for running your product development cycle from end to end.

When you install Ship OS, everything arrives pre-configured. This guide walks you through connecting the Custom Agents that power the workflow.

A few things to keep in mind before you install:

1. Plan: Ship OS uses Notion AI and Custom Agents, so your workspace needs to be on the Business plan or higher. Learn more about our plans→

2. Admin access: If Slack or GitHub isn’t already connected to your workspace, you’ll need an admin to connect them. If you’re not an admin, loop one in. (See the toggle below for how to find yours.)

When you install Ship OS, a parent page lands in your workspace with:

• Databases for your backlog, tasks, docs, meetings, status updates, launches, and release readiness checks.

• Custom Agent templates that handle triage, planning, task generation, coding, status reporting, and go/no-go decisions.

You can place the parent page anywhere in your workspace. Ship OS doesn’t need its own teamspace.

Each Custom Agent ships with instructions already written, so setup is mostly linking agents to the right databases and turning on triggers. You can edit those instructions at any time to match your team’s voice, workflows, or conventions.

Set them up in the order below, which mirrors how work moves through Ship OS. Tools and access is preset for each agent by the template. Your job is to verify it looks right, configure Triggers, and swap a couple of placeholders in each agent's instructions.

Each Custom Agent also has its own setup instructions on the parent page for more detail.

The Product Feedback Triager is a Custom Agent that captures actionable product feedback from Slack into your Product Backlog, creates a new item in the Triage column, and replies in the Slack thread with a link. It runs every time someone posts in your designated feedback channel.

The PRD Drafter is a Custom Agent that turns a backlog item into a first-pass PRD in the Docs database, links it back to the backlog item, and leaves an audit-log comment. It runs whenever a Product Backlog item's Status changes to Plan.

The Engineering Task Generator is a Custom Agent that reads the PRD(s) linked to a backlog item and creates a set of tasks in the Tasks database, each related back to the backlog item and PRD. It runs whenever a Product Backlog item's Status changes to Build.

The Claude Coding Agent is an External Agent (a Claude-powered agent that runs alongside your Notion workflow) that takes a well-scoped task and returns a code change. When it has GitHub write access, it opens a PR. When it doesn't, it drops a patch and instructions for you to open the PR yourself. It runs whenever a task's Status changes to Build.

The Weekly Eng Status Reporter reads the Product Backlog and drafts your team's weekly status update, covering what shipped, what's in flight, and what's blocked. It runs automatically Every Friday at 7:00 AM, and you can invoke it any time by @-mentioning it or chatting with it directly.

The Ship Ops Agent answers "is this ready to ship?" by reading the Product Backlog, Tasks, Docs, and Meetings databases, then flagging what's blocked, unowned, or still open for decision. It runs on demand, so invoke it by @-mentioning it on a page or chatting with it directly.

Here's the path the Dashboard views example request takes from a Slack message to a shipped feature.

1. Triage: A customer request lands in #ship-os-product-feedback; "My customer wants dashboard views to monitor usage across their teams." The Product Feedback Triager creates a Product Backlog item in Triage and replies in the Slack thread with a link.

2. Plan: Drag the item to Plan. The PRD Drafter creates a linked draft in the Docs database with the original Slack message attached. Your team can then refine the PRD and move the work to Build.

3. Build: The Engineering Task Generator creates tasks linked to the PRD. When engineers move a task into Build, the Claude Coding Agent opens a GitHub PR for it. Review and merge as they land.

4. Review and Ship: @-mention the Ship Ops Agent and ask, "Is dashboard views ready to ship?" . It generates a readiness report with links to the supporting work. Once you're ready, move the backlog item to Ship. The Weekly Eng Status Reporter includes it in Friday's update.

Ship OS works out of the box, and most teams start customizing it within their first sprint or two. Here are a few common next moves:

• Add more agents on your codebase: Add Claude agents for PR review, triage, or post-merge follow-up. See How to set up Claude agents on your team's Notion task board for patterns.

• Set up automatic release notes: Add a release-notes agent that reads items in the Ship column and drafts the changelog into the Docs database.

• Update the agent's instructions: If you keep rewriting its response the same way, paste those edits into the instructions, e.g. "always include customer impact in the title."

From there, the most common next steps are adding views and properties that fit how your team thinks about work, and hooking more intake channels into the Product Backlog (Zendesk, GitHub, support inboxes). The Custom Agent best practices guide goes deeper on the iteration loop.