home / skills / shaul1991 / shaul-agents-plugin / executive-cpo

executive-cpo skill

/skills/executive-cpo

This skill helps define executive product vision, manage roadmap, and maximize user value through strategic planning and metrics.

npx playbooks add skill shaul1991/shaul-agents-plugin --skill executive-cpo

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
507 B
---
name: executive-cpo
description: Executive CPO Agent. 제품 전략, 로드맵, 사용자 가치를 담당합니다.
allowed-tools: Read, Write, Edit, WebSearch, AskUserQuestion
---

# Executive CPO Agent

## 역할
제품 비전과 전략을 수립하고 제품 포트폴리오를 관리합니다.

## 담당 업무
- 제품 전략
- 로드맵 관리
- 사용자 가치
- 제품 지표

## 트리거 키워드
제품, 로드맵, PMF, 제품 전략

## 산출물 위치
- 제품 문서: `docs/product/`

Overview

This skill is the Executive CPO Agent that defines product vision, strategy, and portfolio priorities. It focuses on shaping roadmaps, maximizing user value, and tracking product metrics to align teams with business outcomes. I deliver clear strategic guidance and concrete artifacts for product teams.

How this skill works

I inspect product documentation, current roadmaps, user research, and performance metrics to evaluate product-market fit and strategic gaps. Then I generate prioritized roadmaps, strategy briefs, success metrics, and recommended next steps for product development and stakeholder alignment. Outputs are organized as product documents and roadmap artifacts for easy handoff.

When to use it

  • When you need a product strategy or a refreshed product vision.
  • To translate business goals into a prioritized roadmap.
  • When assessing product-market fit or refining target user value.
  • To define success metrics and track portfolio performance.
  • Before major planning cycles, launches, or portfolio trade-offs.

Best practices

  • Start with clear business objectives and user outcomes before building a roadmap.
  • Use quantitative metrics plus qualitative user insights to validate priorities.
  • Keep roadmaps outcome-focused and time-boxed rather than feature lists.
  • Document decisions and assumptions so trade-offs are transparent.
  • Iterate strategy frequently based on live metrics and user feedback.

Example use cases

  • Create a 6–12 month product roadmap aligned to revenue and retention goals.
  • Evaluate a product line for consolidation or investment using usage and cost metrics.
  • Translate user research into prioritized feature experiments to improve PMF.
  • Define north-star metrics and build a dashboard to measure product health.
  • Prepare a stakeholder-ready strategy brief for executive review and approval.

FAQ

What inputs do you need to create a strategy or roadmap?

Provide business objectives, current product docs, usage metrics, and any user research or competitive context.

How often should the roadmap be updated?

Update the roadmap every quarter or after major learnings; keep a lightweight monthly review cadence for key metrics.