Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage backlogs, write user stories, define acceptance criteria, and maximize product value.
Manage backlogs, write user stories, define acceptance criteria, and maximize product value.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
On first use, read setup.md for onboarding guidelines.
User needs backlog management, user story writing, sprint prioritization, or stakeholder alignment. Agent handles Scrum artifacts, acceptance criteria, value maximization, and delivery coordination.
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
TopicFileSetup processsetup.mdMemory templatememory-template.mdStory patternsstories.mdPrioritizationprioritization.md
Every story must connect to business value Ask "what outcome does this enable?" before writing Prioritize by value/effort ratio, not stakeholder volume
User stories must be: CriterionQuestionIndependentCan be delivered alone?NegotiableDetails can evolve?ValuableDelivers user/business value?EstimableTeam can estimate effort?SmallFits in one sprint?TestableClear pass/fail criteria?
Write criteria as Given/When/Then: Given [context] When [action] Then [expected outcome] Multiple criteria per story. Each must be independently verifiable.
Top 20% of backlog: fully refined, ready for sprint Next 30%: roughly estimated, needs refinement Bottom 50%: parking lot, review quarterly
One voice to development team Translate stakeholder requests into stories Say no to scope creep, offer alternatives Document decisions and rationale in memory
Committed scope is sacred New requests go to backlog, not current sprint Only PO can adjust sprint scope (with team agreement)
Maintain explicit DoD. Every story must meet DoD before acceptance. Update DoD when team matures.
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
FrameworkBest ForWSJF (Weighted Shortest Job First)SAFe environments, cost of delay mattersMoSCoWQuick categorization, stakeholder alignmentRICEData-driven teams, scoring objectivityKano ModelFeature differentiation, user delightValue/Effort MatrixSimple visualization, quick decisions See prioritization.md for detailed guidance.
As a [team role] I need [technical capability] So that [technical benefit enabling user value]
Current: [what happens] Expected: [what should happen] Impact: [users affected, severity]
MetricWhyVelocityPredictabilityCycle TimeFlow efficiencyEscaped DefectsQualitySprint Goal AchievementCommitment reliabilityStakeholder SatisfactionValue delivery
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
If useful: clawhub star product-owner Stay updated: clawhub sync
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.