agile-product-owner

Generate INVEST-compliant user stories with Given-When-Then acceptance criteria.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill agile-product-owner-fantasia1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agile-product-owner
Source: https://github.com/Fantasia1999/claude-skills-zh/tree/main/translations/product-team/agile-product-owner
Command: npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill agile-product-owner-fantasia1999

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines product development by providing tools for effective backlog management, user story creation, and iterative planning, ensuring efficient delivery of value.

Core Features & Use Cases

  • User Story Generation: Craft clear, INVEST-compliant user stories with acceptance criteria.
  • Epic Breakdown: Decompose large initiatives into manageable, deliverable stories.
  • Sprint Planning: Calculate team capacity and select stories for iterative execution.
  • Backlog Prioritization: Rank items based on value, effort, and strategic alignment.
  • Use Case: A product owner can use this skill to quickly generate user stories for a new feature, define acceptance criteria using the Given-When-Then format, and then plan the upcoming sprint by estimating story points and allocating capacity.

Quick Start

Use the agile-product-owner skill to write a user story for a new login 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 user stories that follow the INVEST principles?

User stories following INVEST principles are generated by decomposing epics into manageable items, ensuring each story is independent, negotiable, valuable, estimable, small, and testable. Acceptance criteria use the Given-When-Then format for clear requirements.

How do I plan a sprint and calculate team capacity for iterative development?

Sprint planning calculates team capacity and selects user stories for iterative execution by estimating story points and allocating available resources. This ensures realistic sprint plans that align with tracked velocity for iterative development cycles.

What is the best way to prioritize a product backlog based on strategic alignment?

Backlog prioritization ranks items based on value, effort, and strategic alignment. This approach ensures efficient delivery of value by ordering backlog items to maximize return and guide iterative development cycles effectively.

How do I break down large epics into manageable user stories?

Epic breakdown decomposes large initiatives into manageable, deliverable user stories. This process supports iterative development cycles by ensuring epics are split into smaller components that adhere to INVEST principles and Given-When-Then formats.

Can I use this for tracking team velocity during iterative development cycles?

Yes, velocity tracking is supported for iterative development cycles. By calculating team capacity and estimating story points during sprint planning, you can monitor velocity to guide future backlog prioritization and sprint execution.

agile-product-owner: How does it support acceptance criteria creation?

The agile-product-owner skill supports acceptance criteria creation by requiring the Given-When-Then format. This ensures clear requirements and testable conditions are established when generating user stories and decomposing epics.