rig-CPO

The Ulys CPO operations rig — an agent workspace for orchestrating product operations across the company.

What it does

The core mandate is keeping Linear as the source of truth for progress and PRDs as the source of truth for requirements:

• Pull current status on deliverables, projects, and cycles from Linear
• Flag drift — work that's happening but not reflected in Linear (missing issues, stale statuses, unowned or undated work)
• Roll up progress per team/project into leadership-ready summaries
• Daily comms digest (every morning, ~7 AM ET, from Connor's machine): sweep the trailing 24h of public Slack channels, email, and meeting notes for project mentions, and file a dated summary per project in the specs repo

For the team — what you'll see, and how to work with it

You don't need to install or run anything. Here's what's happening and how to make it work for you:

• Every project folder in ulys-product-specs accumulates a daily record of what was said about it, at prds/<project>/comms-digest/YYYY-MM-DD.md — key points, decisions (quoted and linked to the source), open questions, and who was involved.
• DRAFT folders: Linear projects with no PRD yet get a scaffolded folder marked DRAFT — scaffolded from Linear. That's a placeholder for digests to land in, not a reviewed spec. Every Linear project links back to its folder.
• Say the project's name. The sweep matches on project names and obvious aliases in public channels, email, and synced meeting notes. If a discussion matters, name the project in it — "the trading thing" won't be caught; "Advanced Trading" will.
• Decisions in 1:1s or DMs are invisible to it (by design — privacy rules). If you decide something that should persist, restate it in a public channel.
• It records, it doesn't act. A decision appearing in a digest changes nothing in the PRD or Linear by itself. Requirement and status changes still go through the normal process.
• PRD changes get announced. When Connor updates a PRD (directly or via a reviewed rig change), the matching #prj-<project> channel gets a short message from him with the change and a link. Only his own changes are announced this way.
• Spot something wrong in a digest — misattributed, missing, miscited? Call it out in Slack and tag Connor.

Setup

1. Install the rig (or clone this workspace) and run claude from the root.
2. Create me/profile.md with your name, role, and current priorities (local-only).
3. Authenticate the Linear MCP server: run /mcp inside Claude Code and complete the OAuth sign-in (the server is preconfigured in .mcp.json with read/write access).
4. Optional: enable the Gmail connector at the account level (Claude desktop app → Settings → Connectors) for email context. This attaches to your Claude account, not the rig — see CLAUDE.md → MCP access for how the agent treats email.

Layout