OpenParable
Skip to content
← Back to skills

Product Owner

Productivity
product-owner

Product Owner is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Assist Product Owners with idea capture, backlog management, prioritization frameworks, and stakeholder communication. Use when working with product ideas, backlog items, sprint planning, or prioritization decisions. Triggers on keywords like "idea", "backlog", "prioritize", "sprint planning", "user value", "stakeholder", "product vision".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/product-owner-duc01226-easyplatform/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/product-owner, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Product Owner

Role: value-driven decisions, backlog management, stakeholder communication, product vision alignment.

When to Activate

  • Backlog prioritization or ordering decisions
  • Product roadmap or sprint planning
  • Stakeholder communication (sprint reviews, roadmap updates)
  • Idea capture and value assessment

Workflow

  1. Understand product context -- load relevant module docs from docs/business-features/
  2. Route to the appropriate task skill below
  3. Validate output against quality checklist

Task Routing

TaskSkillCommand
Capture ideaidea/idea
Prioritize backlogprioritize/prioritize
Sprint/project statusstatus/status
Track dependenciesdependency/dependency
Refine idea to PBIrefine/refine
Create user storiesstory/story
Quality gate checkquality-gate/quality-gate

⚠️ MUST READ Frameworks Reference

⚠️ MUST READ .claude/skills/shared/team-frameworks.md — RICE, MoSCoW, Value vs Effort matrix.

Business Documentation Paths

ContentPath
Feature Indexdocs/business-features/{Module}/INDEX.md
Module Requirementsdocs/business-features/{Module}/README.md
Idea Templatesteam-artifacts/templates/idea-template.md
PBI Templatesteam-artifacts/templates/pbi-template.md

PO-Specific Guidelines

  • Always use numeric priority ordering (1 = highest), never High/Med/Low categories
  • Focus on user value and business outcomes, not technical implementation details
  • Explicitly list "Out of Scope" to prevent scope creep
  • Identify upstream/downstream dependencies for every PBI
  • Stakeholder communication must quantify or qualify value propositions

Output Conventions

  • Ideas: {YYMMDD}-po-idea-{slug}.md
  • PBIs: {YYMMDD}-pbi-{slug}.md
  • Status values: draft | under_review | approved | rejected | in_progress | done

Quality Checklist

  • Problem statement is user-focused, not solution-focused
  • Value proposition quantified or qualified
  • Priority has numeric order
  • Dependencies explicitly listed
  • Status frontmatter current

IMPORTANT Task Planning Notes

  • Always plan and break many small todo tasks
  • Always add a final review todo task to review the works done at the end to find any fix or enhancement needed