Product Owner

What This Skill Does

The Product Owner skill transforms the OpenClaw AI into a strategic delivery manager for your software projects. It acts as an authoritative, organized proxy between stakeholders and development teams, ensuring that your product development process is guided by measurable business value rather than shifting whims. The skill provides a structured framework for maintaining a healthy backlog, crafting high-quality user stories following the INVEST criteria, and ensuring that every feature has clear, testable acceptance criteria using the Gherkin syntax (Given/When/Then). By leveraging this skill, you formalize how work is refined, prioritized, and communicated, preventing the common pitfalls of scope creep and vague requirements that plague many agile teams.

Installation

To integrate this agent into your workflow, use the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/product-owner Once installed, ensure you have initialized the ~/product-owner/ directory structure as defined in the documentation to allow the agent to persist its memory, stakeholder notes, and sprint history across sessions.

Use Cases

• Backlog Grooming: Automatically categorize and prioritize the bottom 50% of your backlog into a 'parking lot' while ensuring the top 20% are fully refined for immediate development.
• Stakeholder Synthesis: Translate high-level, often vague feature requests from stakeholders into actionable, developer-ready user stories with clear business value.
• Sprint Planning: Manage the sanctity of current sprint boundaries by directing scope creep into the backlog and utilizing prioritization frameworks like RICE or WSJF to maintain velocity.
• Requirement Specification: Generate comprehensive 'Definition of Done' checklists and Gherkin-based acceptance criteria for complex epic features.

Example Prompts

1. "I have a list of raw feature requests from our marketing team. Can you organize these into the backlog file, prioritize them using the RICE framework, and draft three user stories for the top item?"
2. "We are seeing scope creep in the current sprint. Draft a message for the team explaining why we need to move these new requests to the next sprint and help me re-prioritize the backlog to reflect our new business goals."
3. "Review the current stories in the product-owner/backlog/platform.md file and check if they meet the INVEST criteria. Identify any that need better acceptance criteria before we start the next sprint."

Tips & Limitations

• Tip: Always prioritize 'Value over Features'. When in doubt, ask the agent to help you calculate the 'Cost of Delay' for a feature.
• Tip: Treat the memory.md file as the 'single source of truth'. Keep it updated with stakeholder decisions so the agent maintains context.
• Limitation: The agent cannot force team culture changes. It requires the actual development team to adhere to the DoD and sprint boundaries established by the PO.
• Limitation: The efficacy of the agent depends heavily on the accuracy of your file-based memory. Ensure you perform a quarterly cleanup of the backlog to keep data fresh.