skills.rest
anicdh
anicdhCOMMUNITY
Explore all skills by this author →
GitHub

product-owner-review

Classify project plans into user-oriented or technical Epics with dependencies.

1|Updated Mar 30, 2026
Search Tags:#design#planning#epics#agile#backlog#classification#stakeholders
One-click install
npx skills add https://github.com/anicdh/agstack --skill product-owner-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-owner-review
Source: https://github.com/anicdh/agstack/tree/main/.claude/skills/product-owner-review
Command: npx skills add https://github.com/anicdh/agstack --skill product-owner-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn CEO-approved plans into a structured, prioritized backlog by breaking them down into Epics and classifying each as user-oriented or technical, including design gating.

Core Features & Use Cases

  • ** Epic breakdown**: splits large plans into discrete Epics with clear scope.
  • ** Type classification**: automatically classifies Epics as user-oriented or technical based on scope.
  • ** Design gating**: marks Epics that require product design before sprint planning.
  • ** Dependency mapping**: captures sequencing and prerequisites for Epics.

Quick Start

Provide an epic backlog by breaking down the plan and classifying epics as user-oriented or technical, then identify which require design before sprint planning.

Frequently Asked Questions about product-owner-review

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

FAQPage Schema
How do I break down a project plan into ready-to-sprint Epics?▼

Epic breakdown splits large project plans into discrete Epics with clear scope, type classification, and design requirements to prepare your backlog for sprint planning.

What is the best way to classify Epics as user-oriented or technical?▼

Epic classification enforces a default user-oriented type unless all technical epic criteria are met, capturing dependencies and readiness to ensure correct backlog structuring.

How do I identify which Epics require product design before sprint planning?▼

Design gating marks Epics that require product design before sprint planning, ensuring dependencies and prerequisites are captured for backlog readiness.

Can I use PRD documents to generate an agile backlog with mapped dependencies?▼

Reading PRD documents and reviews produces Epic entries with type, design requirements, and scope, while dependency mapping captures sequencing and prerequisites for sprint planning.

When should I map dependencies and prerequisites for my backlog Epics?▼

Dependency mapping captures sequencing and prerequisites for Epics during backlog planning, ensuring all design requirements and readiness criteria are met before sprint execution.

Related Skills

Explore More Product & Management Skills→
bychrisrbychrisr

aiox-pm

Orchestrate product management workflows for PRD generation and epic breakdown.

Community
Advanced
Pact-Community-OrganizationPact-Community-Organization
1

backlog-management

Organize Epics, Stories, and Tasks with readiness criteria for sprint delivery.

Official
Intermediate
striderZAstriderZA
72

story-readiness

Validate game story files for GDD traceability and testable acceptance criteria.

Community
Advanced
C0ntr0lledCha0sC0ntr0lledCha0s
3

planning-sprints

Automate sprint planning and backlog refinement with prioritization frameworks.

Community
Intermediate