agile-product-owner

Create INVEST-compliant user stories with acceptance criteria and sprint sizing plans.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill agile-product-owner-patasse97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agile-product-owner
Source: https://github.com/Patasse97/claude-skills/tree/main/product-team/agile-product-owner
Command: npx skills add https://github.com/Patasse97/claude-skills --skill agile-product-owner-patasse97

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Backlog management and sprint coordination can be time-consuming and error-prone without standardized workflows and templates.

Core Features & Use Cases

  • INVEST-aligned user story templates for backlog items
  • Sprint planning guidance with capacity, commitments, and stretch goals
  • Epic breakdown and acceptance criteria patterns to ensure testable work
  • Reference documents and templates to accelerate planning and delivery

Quick Start

Take a high-level requirement and create an INVEST-compliant user story with acceptance criteria and a plan for sprint sizing.

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 user stories that meet INVEST criteria for an agile backlog?

To create INVEST-compliant user stories, apply standardized templates to high-level requirements, ensuring each backlog item is independent, negotiable, valuable, estimable, small, and testable, while defining clear acceptance criteria for sprint readiness.

What is the best way to plan a sprint using capacity and velocity tracking?

Sprint planning uses standardized workflows to map team capacity against velocity tracking, establishing clear commitments and stretch goals across planning cycles to ensure repeatable and accurate delivery estimations.

How do you break down epics into testable user stories with acceptance criteria?

Epic breakdown involves decomposing large initiatives into smaller user stories using acceptance criteria patterns. This ensures all resulting work is testable, actionable, and ready for sprint sizing and prioritization.

Can I use this backlog management approach for repeatable sprint planning cycles?

Yes, the backlog management approach provides reference documents and standardized workflows that enable repeatable planning and prioritization across multiple sprint cycles, ensuring consistent sprint execution and delivery.

Why does my backlog management lack standardized workflows and templates?

Backlog management becomes time-consuming and error-prone without standardized workflows and templates. Applying structured epic breakdown, user story writing, and sprint planning guidance eliminates coordination errors and accelerates delivery.