agile-product-owner

What This Skill Does

The agile-product-owner skill is a robust toolkit designed to streamline the software development lifecycle. It functions as a virtual product owner, assisting teams in managing their backlogs, refining user stories, and executing sprint planning. By utilizing standardized frameworks like INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable) and Given-When-Then behavioral patterns, the skill ensures that requirements are clear, testable, and aligned with business goals. It handles the heavy lifting of breaking down epics, estimating story points, and defining acceptance criteria to maintain development velocity.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/alirezarezvani/agile-product-owner Ensure you have the necessary permissions to install extensions from the repository.

Use Cases

• Backlog Grooming: Convert vague feature requests into structured, actionable items.
• Sprint Planning: Decompose high-level epics into granular user stories with estimated complexity.
• Quality Assurance: Generate comprehensive testable acceptance criteria to prevent requirements ambiguity.
• Technical Documentation: Standardize the format of technical debt and enabler tasks to align with product roadmap goals.

Example Prompts

1. "Break down the epic 'User Authentication' into smaller user stories, estimate them using Fibonacci points, and provide acceptance criteria for the login flow."
2. "Write an INVEST-compliant user story for a feature that allows users to toggle dark mode in the settings panel."
3. "Review these three user stories for the 'Dashboard' epic and identify any gaps in the acceptance criteria or potential dependencies that might affect sprint velocity."

Tips & Limitations

• Tip: When defining personas, be specific to your domain to ensure the 'Value' component of the story hits the right pain points.
• Tip: Use the Fibonacci scale consistently to maintain reliable velocity tracking over time.
• Limitation: The skill acts as an assistant; final validation of complex technical constraints or business-specific compliance requirements should always be performed by a human Product Owner or stakeholder. Ensure that the generated Given-When-Then scenarios are validated against existing system architecture.