Product Owner workflow for Claude Code

CC-PO lets one person run a repository through Claude Code sessions without reading code. Each product line gets one Product Owner (PO) session. The PO keeps the line's backlog on a GitHub Project, starts a few sub-sessions to do the work, answers their questions, accepts their pull requests, and brings the owner only the decisions that need a person: product choices, risk and Production.

The plugin has three skills:

Skill	Command	What it does
product-owner	/cc-po:product-owner	Runs a PO session: triage, issue fields, sub-session briefs, the acceptance gate before merge, Production steps the owner approved, reporting.
task-claim	/cc-po:task-claim	One writing session per GitHub issue: claim:, checkpoint, handoff:, release: and done: comments, with the earliest claim winning.
setup	/cc-po:setup	Asks a few questions, reads your GitHub Project and writes docs/product-owner-config.md.

The skills are the same text in every repository. Everything your repository decides (owner, report language, board and field ids, lines, branches, required checks, review tools, session limits) lives in one committed file, docs/product-owner-config.md.

Requirements

• Claude desktop app, Code tab, for the full workflow. A PO starts sub-sessions and messages them (start_session, SendMessage, list_sessions), which only the desktop app provides. A terminal-only Claude Code session can use task-claim and the review flow, but cannot run a PO that starts or coordinates sub-sessions.
• GitHub CLI (gh) signed in with the project and read:org scopes (gh auth login --scopes project,read:org), and workflow if sessions dispatch workflows.
• A GitHub Project for the backlog, with Status and Priority fields and, ideally, a single-select Product Line field with one option per line. An iteration field is optional: with one, the POs keep sprints.
• Node.js (optional) to run the config checker.
• GitHub connector (optional). The plugin lists GitHub's remote MCP server (https://api.githubcopilot.com/mcp/) under the name github. On claude.ai and Cowork it appears on the plugin's Connectors tab, where each user connects their own account; Claude Code loads it with the plugin. The skills use gh and never depend on it. If you also have the official github plugin, both declare a server named github, so you may see it twice; keep either one.
• Optional reviewers. The skills run whatever your config lists in local_reviews; without any, sessions use a fresh-context subagent review. The Codex plugin for Claude Code and its CLI work well as one of them (agents run codex review -c model_reasoning_effort=<level> --base origin/<branch>, with the level from subagent_effort).

Install

In Claude Code, inside your repository:

/plugin marketplace add JOY/CC-PO
/plugin install cc-po@cc-po

To enable it for everyone who works in the repository, install it at project scope from a terminal and commit .claude/settings.json:

claude plugin marketplace add JOY/CC-PO --scope project
claude plugin install cc-po@cc-po --scope project

Each further machine runs the same two commands once; Claude Code does not install a plugin from another repository by itself.

Antigravity

The same plugins/cc-po directory also ships an Antigravity manifest (plugin.json) and host rules (rules/AGENTS.md) alongside the Claude Code files, with no changes to the skills themselves. Copy plugins/cc-po into ~/.gemini/config/plugins/cc-po (or .agents/plugins/cc-po in a repository; on Windows, copy a real directory rather than an NTFS junction, which Antigravity's plugin scanner skips), then restart Antigravity so it discovers the plugin:

# Windows (PowerShell)
Copy-Item -Recurse -Force "<path to CC-PO>\plugins\cc-po" "$env:USERPROFILE\.gemini\config\plugins\cc-po"

# macOS / Linux
cp -R "<path to CC-PO>/plugins/cc-po" ~/.gemini/config/plugins/cc-po

What stays the same and what differs on Antigravity:

This is the beginning of the README. Read the rest at the original. Read the full README ↗