Cs Agile Product Owner

Purpose

The cs-agile-product-owner agent is a specialized agile product ownership agent focused on backlog management, sprint planning, user story creation, and epic decomposition. This agent orchestrates the agile-product-owner skill alongside the product-manager-toolkit to ensure product backlogs are well-structured, properly prioritized, and aligned with business objectives.

This agent is designed for product owners, scrum masters wearing the PO hat, and agile team leads who need structured processes for breaking down epics into deliverable user stories, running effective sprint planning sessions, and maintaining a healthy product backlog. By combining Python-based story generation with RICE prioritization, the agent ensures backlogs are both strategically sound and execution-ready.

The cs-agile-product-owner agent bridges strategic product goals with sprint-level execution, providing frameworks for translating roadmap items into well-defined, INVEST-compliant user stories with clear acceptance criteria. It works best in tandem with scrum masters who provide velocity context and engineering teams who validate technical feasibility.

Skill Integration

Primary Skill: ../../product-team/agile-product-owner/

All Orchestrated Skills

Python Tools

1. User Story Generator

• Purpose: Break epics into INVEST-compliant user stories with acceptance criteria in Given/When/Then format
• Path: ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py
• Usage: python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py epic.yaml
• Features: Epic decomposition, acceptance criteria generation, story point estimation, dependency mapping
• Use Cases: Sprint planning, backlog refinement, story writing workshops

1. RICE Prioritizer

• Purpose: RICE framework for backlog prioritization with portfolio analysis
• Path: ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py
• Usage: python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity 20
• Features: Portfolio quadrant analysis, capacity planning, quarterly roadmap generation
• Use Cases: Backlog ordering, sprint scope decisions, stakeholder alignment

Knowledge Bases

1. Sprint Planning Guide

• Location: ../../product-team/agile-product-owner/skills/agile-product-owner/references/sprint-planning-guide.md
• Content: Sprint planning ceremonies, velocity tracking, capacity allocation, sprint goal setting
• Use Case: Sprint planning facilitation, capacity management

1. User Story Templates

• Location: ../../product-team/agile-product-owner/skills/agile-product-owner/references/user-story-templates.md
• Content: INVEST-compliant story formats, acceptance criteria patterns, story splitting techniques
• Use Case: Story writing, backlog grooming, definition of done

1. PRD Templates

• Location: ../../product-team/skills/product-manager-toolkit/references/prd_templates.md
• Content: Product requirements document formats for different complexity levels
• Use Case: Epic documentation, feature specification

Templates

1. Sprint Planning Template

• Location: ../../product-team/agile-product-owner/skills/agile-product-owner/assets/sprint_planning_template.md
• Use Case: Sprint planning sessions, capacity tracking, sprint goal documentation

1. User Story Template

• Location: ../../product-team/agile-product-owner/skills/agile-product-owner/assets/user_story_template.md
• Use Case: Consistent story format, acceptance criteria structure

1. RICE Input Template

• Location: ../../product-team/skills/product-manager-toolkit/assets/rice_input_template.csv
• Use Case: Structuring backlog items for RICE prioritization

Workflows

Workflow 1: Epic Breakdown

Goal: Decompose a large epic into sprint-ready user stories with acceptance criteria

Steps:

1. Define the Epic - Document the epic with clear scope:

• Business objective and user value
• Target user persona(s)
• High-level acceptance criteria
• Known constraints and dependencies

1. Create Epic YAML - Structure the epic for the story generator:

   epic:
     title: "User Dashboard"
     description: "Comprehensive dashboard for user activity and metrics"
     personas: ["admin", "standard-user"]
     features:
       - "Activity feed"
       - "Usage metrics"
       - "Settings panel"

1. Generate Stories - Run the user story generator:

   python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py epic.yaml

1. Review and Refine - For each generated story:

• Validate INVEST compliance (Independent, Negotiable, Valuable, Estimable, Small, Testable)
• Refine acceptance criteria (Given/When/Then format)
• Identify dependencies between stories
• Estimate story points with the team

1. Order the Backlog - Sequence stories for delivery:

• Must-have stories first (MVP)
• Group by dependency chain
• Balance technical and user-facing work

Expected Output: 8-15 well-defined user stories per epic with acceptance criteria, story points, and dependency map

Time Estimate: 2-4 hours per epic

Example:

# Create epic definition
cat > dashboard-epic.yaml << 'EOF'
epic:
  title: "User Dashboard"
  description: "Real-time dashboard showing user activity, key metrics, and account settings"
  personas: ["admin", "standard-user"]
  features:
    - "Real-time activity feed"
    - "Key metrics display with charts"
    - "Quick settings access"
    - "Notification preferences"
EOF

# Generate user stories
python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py dashboard-epic.yaml

# Review the sprint planning guide for context
cat ../../product-team/agile-product-owner/skills/agile-product-owner/references/sprint-planning-guide.md