skills.rest
Omar-Obando
Omar-ObandoCOMMUNITY
Explore all skills by this author →
GitHub

product-owner

Structure user stories and acceptance criteria for agile backlog refinement.

44|9|Updated May 7, 2026
Search Tags:#acceptance criteria#user stories#product backlog#kanban#agile prioritization#scrum planning
One-click install
npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill product-owner-omar-obando
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-owner
Source: https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/product-owner
Command: npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill product-owner-omar-obando

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product roadmaps fail when backlogs are disorganized and requirements are vague, causing misaligned sprint goals and delivery of low-value work.

Core Features & Use Cases

  • Backlog management & grooming: Maintain an ordered product backlog, refine upcoming stories, and identify dependencies.
  • User story & acceptance criteria definition: Write stories with INVEST-aligned, specific, and testable acceptance criteria.
  • Feature prioritization & sprint planning: Use MoSCoW and Value/Effort or RICE to choose what to deliver and plan sprint work predictably across Scrum/Kanban/scrumban approaches.

Quick Start

Ask an AI assistant to help you write 3 user stories for your next sprint with acceptance criteria and MoSCoW priority based on your product goals.

Frequently Asked Questions about product-owner

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

FAQPage Schema
How do I write user stories with testable acceptance criteria for sprint planning?▼

To write user stories for sprint planning, structure requirements using INVEST-aligned criteria to ensure each story is specific, testable, and includes estimates and priority for actionable sprint selection.

What is the best way to prioritize a product backlog using MoSCoW or RICE?▼

The best way to prioritize a product backlog is by applying frameworks like MoSCoW, Value/Effort, or RICE to evaluate items, ensuring your team delivers high-value work and aligns with predictable sprint goals.

How does structuring user stories help with disorganized product backlogs?▼

Structuring user stories resolves disorganized product backlogs by replacing vague requirements with clear story templates and testable acceptance criteria, preventing misaligned sprint goals and low-value delivery.

Can I use agile prioritization techniques for hybrid Scrumban workflows?▼

Yes, agile prioritization techniques apply to hybrid Scrumban workflows, allowing you to manage backlog refinement and feature prioritization seamlessly across Scrum, Kanban, and mixed agile environments.

When do I need INVEST-style acceptance criteria for backlog refinement?▼

You need INVEST-style acceptance criteria during backlog refinement when you must define specific, testable conditions for user stories, identify dependencies, and prepare ordered stories for upcoming sprints.

Related Skills

Explore More Product & Management Skills→
NikitaITNikitaIT

role-product-owner

Manages product backlog and sprint execution with Scrum and Backlog Abstraction Tree principles.

Community
Advanced
tapanshahtapanshah

agile-product-owner

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

Community
Intermediate
MyHeavenDyfMyHeavenDyf

kanban-board

Generate an interactive kanban board with HTML and JavaScript.

Community
Intermediate
fengqiliufengqiliu
2

pm-alpha-requirement-analysis

Analyze product requirements into user story maps, RICE scores, feasibility, and compliance checks.

Community
Intermediate