product-owner

Decompose product goals into structured epics and stories in plan/.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dlepaux/dotfiles --skill product-owner-dlepaux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-owner
Source: https://github.com/dlepaux/dotfiles/tree/main/.claude/skills/product-owner
Command: npx skills add https://github.com/dlepaux/dotfiles --skill product-owner-dlepaux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose vague product goals into structured epics and stories so teams can plan, prioritize, and execute with clarity.

Core Features & Use Cases

  • Turn a vision into a plan: generate epics and a story table that map to concrete work in plan/
  • Manage scope and priorities: define out-of-scope, dependencies, and acceptance criteria to prevent scope creep
  • Modes for workflow: create, refine, close, migrate, and review to cover the full product lifecycle

Quick Start

Provide a product intent and the system will generate a structured plan in plan/ with epics and stories following the conventions.

Frequently Asked Questions about product-owner

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

FAQPage Schema
How do I break down product goals into structured epics and user stories?

To break down product goals, provide a product intent to generate a structured plan containing epics, user stories, acceptance criteria, and out-of-scope definitions. This decomposition enables disciplined backlog management and traceable work items.

What is the best way to manage backlog scope creep during the planning process?

The best way to manage backlog scope creep is to enforce out-of-scope definitions, dependencies, and acceptance criteria for each epic and story. This structured decomposition prevents vague product goals from expanding unchecked.

Can I refine and close existing epics without regenerating the entire plan?

Yes, you can refine and close existing epics without regenerating the entire plan by using the dedicated refine and close workflow modes. These modes cover the full product lifecycle, allowing you to update work items and track progress independently.

How does epic decomposition align with a north star product vision?

Epic decomposition aligns with a north star product vision by mapping generated epics and story tables directly to concrete work items within the plan directory. This ensures every structured work item enforces alignment with the NORTH-STAR.md document.

Do I need a specific project format to generate user stories and acceptance criteria?

You need a product intent and a plan directory to generate user stories and acceptance criteria. The system enforces structured work items within this plan folder, requiring no additional dependencies or specific external project formats to operate.