Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计通过

product-owner产品负责人

Agent Skill

product-owner 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

15,429

周安装

656

GitHub Stars

公开资料未说明

下载量

5,405
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:product-owner(产品负责人)
来源仓库:https://github.com/ivangdavila/product-owner
安装命令:
openclaw skills install product-owner
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install product-owner

简介

product-owner 协助管理待办事项、编写用户故事并定义验收标准。

  • 适用于敏捷团队中明确任务边界、提升交付效率和价值对齐。
  • 支持拆分复杂需求为可执行条目,并提供优先级评估参考。
  • 安装命令:openclaw skills install product-owner;需接入项目管理工具如 Jira 或 Trello。
  • 注意权限控制,确保仅对授权项目空间进行操作。

SKILL.md

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

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 ~/product-owner/. See memory-template.md for structure.

~/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

TopicFile
Setup processsetup.md
Memory templatememory-template.md
Story patternsstories.md
Prioritizationprioritization.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:

CriterionQuestion
IndependentCan be delivered alone?
NegotiableDetails can evolve?
ValuableDelivers user/business value?
EstimableTeam can estimate effort?
SmallFits in one sprint?
TestableClear 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

FrameworkBest For
WSJF (Weighted Shortest Job First)SAFe environments, cost of delay matters
MoSCoWQuick categorization, stakeholder alignment
RICEData-driven teams, scoring objectivity
Kano ModelFeature differentiation, user delight
Value/Effort MatrixSimple 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

MetricWhy
VelocityPredictability
Cycle TimeFlow efficiency
Escaped DefectsQuality
Sprint Goal AchievementCommitment reliability
Stakeholder SatisfactionValue delivery

Related Skills

Install with clawhub install <slug> if user confirms:

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

Feedback

  • If useful: clawhub star product-owner
  • Stay updated: clawhub sync

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

84.26%
按下载量换算4,554

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills