agile-product-owner

Guide creation of INVEST-compliant user stories with acceptance criteria.

2|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/zhangzhang-111-i/claude-skills111 --skill agile-product-owner-zhangzhang-111-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agile-product-owner
Source: https://github.com/zhangzhang-111-i/claude-skills111/tree/main/product-team/agile-product-owner
Command: npx skills add https://github.com/zhangzhang-111-i/claude-skills111 --skill agile-product-owner-zhangzhang-111-i

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines agile product ownership by providing structured workflows for backlog management, user story creation, and sprint execution, ensuring clarity and efficiency.

Core Features & Use Cases

  • User Story Writing: Craft clear, INVEST-compliant user stories with acceptance criteria.
  • Epic Breakdown: Decompose large epics into manageable, sprint-sized stories.
  • Sprint Planning: Optimize sprint capacity, prioritize backlog items, and track velocity.
  • Use Case: A product owner needs to write a new user story for a feature. They can use this Skill to generate a well-defined story, including acceptance criteria in the Given-When-Then format, and estimate its story points.

Quick Start

Use the agile product owner skill to write a user story for a new feature.

Frequently Asked Questions about agile-product-owner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write INVEST-compliant user stories with acceptance criteria?

INVEST-compliant user stories require structuring features with clear acceptance criteria, typically in Given-When-Then format, and estimating story points to ensure each item is independent, negotiable, valuable, estimable, small, and testable for sprint execution.

What is the best way to break down large epics into sprint-sized stories?

Breaking down large epics involves decomposing them into manageable, sprint-sized user stories that adhere to agile methodologies. This ensures each story carries clear value, has defined acceptance criteria, and fits within sprint velocity constraints for iterative development.

How do I plan sprint capacity and prioritize my agile backlog?

Sprint planning and backlog prioritization are achieved by evaluating team velocity against story point estimates, ordering backlog items by value, and selecting items that fit available sprint capacity to optimize iterative product delivery.

Can I track team velocity for iterative development processes?

Yes, velocity tracking is supported by monitoring completed story points across sprints. This data informs future sprint planning, helps optimize capacity allocation, and ensures backlog prioritization aligns with agile delivery expectations.

Do I need prior Scrum experience to manage backlog items effectively?

Adherence to agile methodologies and best practices is required for efficient product delivery. While structured workflows guide backlog management and sprint execution, foundational understanding of Scrum processes ensures proper epic breakdown and user story creation.