---
name: product-owner-8ef249ebfada
slug: product-owner
version: 1.0.1
description: Manage backlogs, write user stories, define acceptance criteria, and maximize product value.
homepage: https://clawic.com/skills/product-owner
changelog: Improved setup flow with natural conversation guidelines
metadata:
  clawdbot:
    emoji: 📋
    requires:
      bins: []
    os:
    - linux
    - darwin
    - win32
    displayName: Product Owner
---

## Setup

On first use, read `setup.md` for onboarding guidelines.

## When to Use

User needs backlog management, user story writing, sprint prioritization, or stakeholder alignment. Agent handles Scrum artifacts, acceptance criteria, value maximization, and delivery coordination.

## Architecture

Memory lives in `~/Clawic/data/product-owner/`. See `memory-template.md` for structure.

```
~/Clawic/data/product-owner/
├── memory.md          # Product context, stakeholders, priorities
├── backlog/           # Per-product backlogs
│   └── {product}.md   # Stories, priorities, acceptance criteria
└── sprints/           # Sprint history and retrospectives
```

## Quick Reference

| Topic | File |
|-------|------|
| Setup process | `setup.md` |
| Memory template | `memory-template.md` |
| Story patterns | `stories.md` |
| Prioritization | `prioritization.md` |

## Core Rules

### 1. Value Over Features
- Every story must connect to business value
- Ask "what outcome does this enable?" before writing
- Prioritize by value/effort ratio, not stakeholder volume

### 2. INVEST in Stories
User stories must be:
| Criterion | Question |
|-----------|----------|
| Independent | Can be delivered alone? |
| Negotiable | Details can evolve? |
| Valuable | Delivers user/business value? |
| Estimable | Team can estimate effort? |
| Small | Fits in one sprint? |
| Testable | Clear pass/fail criteria? |

### 3. Acceptance Criteria Format
Write criteria as Given/When/Then:
```
Given [context]
When [action]
Then [expected outcome]
```

Multiple criteria per story. Each must be independently verifiable.

### 4. Backlog Grooming Cadence
- Top 20% of backlog: fully refined, ready for sprint
- Next 30%: roughly estimated, needs refinement
- Bottom 50%: parking lot, review quarterly

### 5. Stakeholder Management
- One voice to development team
- Translate stakeholder requests into stories
- Say no to scope creep, offer alternatives
- Document decisions and rationale in memory

### 6. Sprint Boundaries
- Committed scope is sacred
- New requests go to backlog, not current sprint
- Only PO can adjust sprint scope (with team agreement)

### 7. Definition of Done
Maintain explicit DoD. Every story must meet DoD before acceptance. Update DoD when team matures.

## Common Traps

- Writing solutions instead of problems in stories
- Accepting vague requirements without clarification
- Overloading sprints with "just one more thing"
- Prioritizing by who shouts loudest
- Skipping acceptance criteria because "it's obvious"
- Treating estimates as commitments

## Prioritization Frameworks

| Framework | Best For |
|-----------|----------|
| WSJF (Weighted Shortest Job First) | SAFe environments, cost of delay matters |
| MoSCoW | Quick categorization, stakeholder alignment |
| RICE | Data-driven teams, scoring objectivity |
| Kano Model | Feature differentiation, user delight |
| Value/Effort Matrix | Simple visualization, quick decisions |

See `prioritization.md` for detailed guidance.

## Story Templates

### Standard User Story
```
As a [user type]
I want [capability]
So that [benefit]

Acceptance Criteria:
- Given... When... Then...
- Given... When... Then...
```

### Technical Story
```
As a [team role]
I need [technical capability]
So that [technical benefit enabling user value]
```

### Bug Fix
```
Current: [what happens]
Expected: [what should happen]
Impact: [users affected, severity]
```

## Metrics to Track

| Metric | Why |
|--------|-----|
| Velocity | Predictability |
| Cycle Time | Flow efficiency |
| Escaped Defects | Quality |
| Sprint Goal Achievement | Commitment reliability |
| Stakeholder Satisfaction | Value delivery |

## Related Skills
More Clawic skills, get them at https://clawic.com/skills/<slug> (install if the user confirms):

- `product-manager` — Product strategy and roadmap
- `cpo` — Chief Product Officer leadership
- `delegate` — Task delegation patterns
- `business` — Business strategy fundamentals

## Feedback

- If useful, star it: https://clawic.com/skills/product-owner
- Latest version: https://clawic.com/skills/product-owner


---
Source attribution: clawic
Original project: https://github.com/clawic/skills/blob/f825206afbf1c697202533a9187be68c7b697e0e/skills/product-owner/SKILL.md
License: MIT
License information: https://opensource.org/license/mit
Original upstream instructions; downloaded from Mega AI Hub.

## Upstream license notice

MIT License

Copyright (c) 2026 Ivan G. Davila

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.



# Mega AI Hub resource metadata

Creator / publisher: clawic
Original project: https://github.com/clawic/skills/blob/f825206afbf1c697202533a9187be68c7b697e0e/skills/product-owner/SKILL.md
Attribution basis: Source repository record

Fields of work: Product Management, Project & Program Management
Roles: Product Owner, Project Manager, Scrum Master
Specialties: Specialty not specified
Tools: Tool not specified
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: 694f87c46f53948b129fa1761620575105535e0110c0a8350244a86e11166f6f