# Role Po

> Use when a work package needs cutting, acceptance criteria need defining, a new idea needs evaluating (idea triage), or scope creep must be prevented — or when autonomous-loop requests the PO step. Not for implementation or portfolio prioritization.

- **Type:** Skill
- **Install:** `agentstack add skill-bechsteindigital-claude-shiploop-role-po`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [BechsteinDigital](https://agentstack.voostack.com/s/bechsteindigital)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [BechsteinDigital](https://github.com/BechsteinDigital)
- **Source:** https://github.com/BechsteinDigital/claude-shiploop/tree/main/role-po
- **Website:** https://www.bechstein.digital

## Install

```sh
agentstack add skill-bechsteindigital-claude-shiploop-role-po
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 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
1. `project/BRIEF.md` — core contract (must-have outcomes, non-goals, value filter)
2. `project/STATE.md`
3. the one approved WORK item (`project/backlog/WORK-NNN.md`)
4. `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.

| Rationalization | Reality |
|---|---|
| "The idea is small, I'll take it along quickly" | Small × often = sprawl. Funnel, cooling-off, then decide. |
| "It fits the theme perfectly" | Thematically fitting ≠ strengthens a must-have outcome. Apply the value filter. |
| "Without it the MVP feels unfinished" | Must-have outcomes define "finished", not the feeling. Score the core contribution honestly. |
| "The DEV already half built it" | Sunk cost. Zone violated → finding; idea back into the funnel. |

## Set complexity (drives model choice and review depth)
Every card gets an honest complexity: **S/M** = mechanically implementable with the criteria;
**L or "sensitive"** = requires architecture, security, or concurrency judgment, public API affected.
Understating saves tokens and costs quality — when in doubt, rate higher.

## Output (WORK card per `_shared/templates/WORK_ITEM.template.md`)
Scope · problem · goal · non-goals · acceptance criteria · claim limits · claim zone · complexity · risks · follow-up work (proposal only) · exactly one next DEV step.

## Prohibitions
- No scope inflation, no multi-mission cards
- No deep technical designs
- No unclear acceptance criteria, no implicit DONE claims
- No idea handed to DEV that didn't pass triage

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [BechsteinDigital](https://github.com/BechsteinDigital)
- **Source:** [BechsteinDigital/claude-shiploop](https://github.com/BechsteinDigital/claude-shiploop)
- **License:** MIT
- **Homepage:** https://www.bechstein.digital

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-bechsteindigital-claude-shiploop-role-po
- Seller: https://agentstack.voostack.com/s/bechsteindigital
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.