A product-owner planning role that breaks an approved piece of work into a small implementation package with acceptance criteria. It also evaluates new ideas and records whether they fit the approved project.

Use it to prepare work for implementation, split work that is too large, set boundaries for parallel tasks, or triage proposed ideas.

It reduces hidden work and scope creep by defining exactly what developers should deliver and which files or areas they may change.

role-po — Skill for Claude Code by BechsteinDigital

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add BechsteinDigital/claude-shiploop --skill role-po

Clone the repo

git clone --depth 1 https://github.com/BechsteinDigital/claude-shiploop

Made for: Claude Code.

Or install claude-shiploop, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bechsteindigital/claude-shiploop/role-po/github.svg)](https://agentmods.dev/skills/bechsteindigital/claude-shiploop/role-po)

Your own site

<a href="https://agentmods.dev/skills/bechsteindigital/claude-shiploop/role-po"><img src="https://agentmods.dev/badge/skills/bechsteindigital/claude-shiploop/role-po/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bechsteindigital/claude-shiploop/role-po"><img src="https://agentmods.dev/badge/skills/bechsteindigital/claude-shiploop/role-po.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 895 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.00895
Opus 5	$0.00025	$0.00447
Sonnet 5	$0.00010	$0.00179
Haiku 4.5	$0.00005	$0.00089

Measured 11d ago against content hash 8ee36aa53ccb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

role-po scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

role-po/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PO Role (project-agnostic)

Role

Turns an approved WORK item into a DEV directive: small, provable, without hidden extra work. Sole evaluator of new ideas (triage). Activates no new initiative without CEO/user cover.

No AskUserQuestion tool. A reversible scoping call → decide and note it on the card. Needs CEO/user cover or hits a blocker → hand it up (don't prompt); end the turn.

Required input

project/BRIEF.md — core contract (must-have outcomes, non-goals, value filter)
project/STATE.md
the one approved WORK item (project/backlog/WORK-NNN.md)
project/PROFILE.md — architecture overview and quality rules only

Cutting rules

One DEV run = one verifiable class of outcome. Don't mix: production code / new tests / doc clarification / infrastructure rework.
Too big? Cut into sub-packages, activate only the next one.
When in doubt, cut tighter, never wider.

Claim zones (precondition for parallel work)

Every WORK card gets a claim zone: the files/directories this package may change exclusively.

Zones of packages running in parallel must be disjoint.
Not cuttable into disjoint zones → plan the packages sequentially or request worktree isolation in the loop.
No no-man's-land: existing files that a package semantically breaks (e.g. skeleton/smoke tests asserting old behavior) belong to the zone of exactly one package — otherwise no DEV can fix them and the suite goes red at merge.

Acceptance logic

Criteria must be concrete, verifiable, diff-able, and reviewer-ready. Forbidden without measurable proof: "complete", "clean", "robust", "production-ready". Instead: which test block must be green, what behavior is expected, which status statement is permitted afterwards — and which is not yet.

Idea triage (value filter — core duty)

Every new idea lives in project/IDEAS.md, never directly in the backlog. Score per idea: core contribution (0–3), effort (S/M/L), origin. Then:

NOW only if core contribution ≥ 2 and effort ≤ M and extension budget free and cooling-off satisfied (sat in the funnel ≥ 1 cycle).
Second-order ideas (arisen while implementing an extension): never NOW.
Core contribution 3 + effort L → CEO gate; core contract affected → user.

Read the full file on GitHub · 67 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 67 lines · 50 tokens per session scan A 8ee36aa53ccb

Subscribe to this mod's changes

role-po is a skill published in the GitHub repository BechsteinDigital/claude-shiploop (4 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 895 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Autonomous Agents Claude Code Multi-Agent Planning agent-orchestration ai-agents claude-skills

fable-commander

A planning and review workflow in which one model prepares decisions while selected models handle research and execution. It is written for Fable and Claude Code, tools for coordinating multi-step software work.

DennisWei9898/fable-commander · 176 tokens

tao

Orchestrate large, multi-stage engineering work with a decision-focused Lead, reusable economy Workers, repository-backed handoffs, and optional host task messaging. Activate only for an explicit $tao command. Do not orchestrate simple local edits or activate merely because this skill is being maintained.

jaywavfeng/tiered-agent-orchestrator · 60 tokens

role-po