agile-product-owner

Convert requirements into INVEST-aligned user stories and backlog items.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/hongmaple0820/agent-academy --skill agile-product-owner-hongmaple0820
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agile-product-owner
Source: https://github.com/hongmaple0820/agent-academy/tree/main/skills/pm-product/product-team/agile-product-owner
Command: npx skills add https://github.com/hongmaple0820/agent-academy --skill agile-product-owner-hongmaple0820

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agile Product Owner helps teams convert vague ideas into clear, INVEST-aligned user stories, ensuring backlog health and predictable sprint delivery.

Core Features & Use Cases

  • User story generation and refinement from requirements
  • Acceptance criteria patterns and INVEST validation
  • Epic breakdown and sprint planning workflows
  • Backlog prioritization and risk-aware decision making
  • Practical referencing and guidelines to align stakeholders
  • Tools and templates for rapid storytelling and planning

Quick Start

Provide a new user story by describing a feature as a persona and defining acceptance criteria.

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 criteria for agile sprints?

To write user stories using the INVEST criteria, define a feature as a specific persona and outline clear acceptance criteria. This ensures backlog items are independent, negotiable, valuable, estimable, small, and testable for reliable sprint planning.

What is the best way to break down epics into actionable sprint backlog items?

Breaking down epics involves applying standardized templates to split large requirements into smaller, INVEST-aligned user stories. This epic breakdown process ensures backlog items are properly sized for sprint planning and velocity tracking.

How do I structure acceptance criteria for user stories during backlog grooming?

Structure acceptance criteria for user stories by applying standardized templates during backlog grooming. These patterns clarify expected behavior, align stakeholders on value delivery, and validate story readiness for upcoming sprint planning.

Can I use this approach to prioritize a vague product backlog before sprint planning?

Yes, you can prioritize a vague product backlog by converting rough ideas into INVEST-aligned user stories. This approach supports risk-aware decision making and backlog prioritization to align stakeholders before sprint planning begins.

Why does my agile team struggle with predictable sprint delivery and vague requirements?

Teams struggle with predictable sprint delivery when vague ideas lack INVEST-aligned user stories and clear acceptance criteria. Converting requirements into structured backlog items ensures backlog health and reliable sprint outcomes.

When should I apply standardized templates for user story generation in agile?

Apply standardized templates for user story generation whenever you need to elaborate features, define acceptance criteria, or align stakeholders during backlog grooming and sprint planning to ensure reliable value delivery.