{"skill":{"slug":"product-owner","displayName":"Product Owner","summary":"Manage backlogs, write user stories, define acceptance criteria, and maximize product value.","description":"---\nname: Product Owner\nslug: product-owner\nversion: 1.0.1\nchangelog: Improved setup flow with natural conversation guidelines\nhomepage: https://clawic.com/skills/product-owner\ndescription: Manage backlogs, write user stories, define acceptance criteria, and maximize product value.\nmetadata: {\"clawdbot\":{\"emoji\":\"📋\",\"requires\":{\"bins\":[]},\"os\":[\"linux\",\"darwin\",\"win32\"]}}\n---\n\n## Setup\n\nOn first use, read `setup.md` for onboarding guidelines.\n\n## When to Use\n\nUser needs backlog management, user story writing, sprint prioritization, or stakeholder alignment. Agent handles Scrum artifacts, acceptance criteria, value maximization, and delivery coordination.\n\n## Architecture\n\nMemory lives in `~/product-owner/`. See `memory-template.md` for structure.\n\n```\n~/product-owner/\n├── memory.md          # Product context, stakeholders, priorities\n├── backlog/           # Per-product backlogs\n│   └── {product}.md   # Stories, priorities, acceptance criteria\n└── sprints/           # Sprint history and retrospectives\n```\n\n## Quick Reference\n\n| Topic | File |\n|-------|------|\n| Setup process | `setup.md` |\n| Memory template | `memory-template.md` |\n| Story patterns | `stories.md` |\n| Prioritization | `prioritization.md` |\n\n## Core Rules\n\n### 1. Value Over Features\n- Every story must connect to business value\n- Ask \"what outcome does this enable?\" before writing\n- Prioritize by value/effort ratio, not stakeholder volume\n\n### 2. INVEST in Stories\nUser stories must be:\n| Criterion | Question |\n|-----------|----------|\n| Independent | Can be delivered alone? |\n| Negotiable | Details can evolve? |\n| Valuable | Delivers user/business value? |\n| Estimable | Team can estimate effort? |\n| Small | Fits in one sprint? |\n| Testable | Clear pass/fail criteria? |\n\n### 3. Acceptance Criteria Format\nWrite criteria as Given/When/Then:\n```\nGiven [context]\nWhen [action]\nThen [expected outcome]\n```\n\nMultiple criteria per story. Each must be independently verifiable.\n\n### 4. Backlog Grooming Cadence\n- Top 20% of backlog: fully refined, ready for sprint\n- Next 30%: roughly estimated, needs refinement\n- Bottom 50%: parking lot, review quarterly\n\n### 5. Stakeholder Management\n- One voice to development team\n- Translate stakeholder requests into stories\n- Say no to scope creep, offer alternatives\n- Document decisions and rationale in memory\n\n### 6. Sprint Boundaries\n- Committed scope is sacred\n- New requests go to backlog, not current sprint\n- Only PO can adjust sprint scope (with team agreement)\n\n### 7. Definition of Done\nMaintain explicit DoD. Every story must meet DoD before acceptance. Update DoD when team matures.\n\n## Common Traps\n\n- Writing solutions instead of problems in stories\n- Accepting vague requirements without clarification\n- Overloading sprints with \"just one more thing\"\n- Prioritizing by who shouts loudest\n- Skipping acceptance criteria because \"it's obvious\"\n- Treating estimates as commitments\n\n## Prioritization Frameworks\n\n| Framework | Best For |\n|-----------|----------|\n| WSJF (Weighted Shortest Job First) | SAFe environments, cost of delay matters |\n| MoSCoW | Quick categorization, stakeholder alignment |\n| RICE | Data-driven teams, scoring objectivity |\n| Kano Model | Feature differentiation, user delight |\n| Value/Effort Matrix | Simple visualization, quick decisions |\n\nSee `prioritization.md` for detailed guidance.\n\n## Story Templates\n\n### Standard User Story\n```\nAs a [user type]\nI want [capability]\nSo that [benefit]\n\nAcceptance Criteria:\n- Given... When... Then...\n- Given... When... Then...\n```\n\n### Technical Story\n```\nAs a [team role]\nI need [technical capability]\nSo that [technical benefit enabling user value]\n```\n\n### Bug Fix\n```\nCurrent: [what happens]\nExpected: [what should happen]\nImpact: [users affected, severity]\n```\n\n## Metrics to Track\n\n| Metric | Why |\n|--------|-----|\n| Velocity | Predictability |\n| Cycle Time | Flow efficiency |\n| Escaped Defects | Quality |\n| Sprint Goal Achievement | Commitment reliability |\n| Stakeholder Satisfaction | Value delivery |\n\n## Related Skills\nInstall with `clawhub install <slug>` if user confirms:\n\n- `product-manager` — Product strategy and roadmap\n- `cpo` — Chief Product Officer leadership\n- `delegate` — Task delegation patterns\n- `business` — Business strategy fundamentals\n\n## Feedback\n\n- If useful: `clawhub star product-owner`\n- Stay updated: `clawhub sync`\n","tags":{"latest":"1.0.1"},"stats":{"comments":0,"downloads":808,"installsAllTime":0,"installsCurrent":0,"stars":0,"versions":1},"createdAt":1771759481965,"updatedAt":1778491608600},"latestVersion":{"version":"1.0.1","createdAt":1771759481965,"changelog":"Improved setup flow with natural conversation guidelines","license":null},"metadata":{"setup":[],"os":["linux","darwin","win32"],"systems":null},"owner":{"handle":"ivangdavila","userId":"s178jdk12x4qj3gs2se3etxf3h83h7ft","displayName":"Iván","image":"https://avatars.githubusercontent.com/u/81719670?v=4"},"moderation":null}