Run any Skill in Manus with one click

cpo-playbook

Stars4

Forks0

UpdatedApril 1, 2026 at 16:20

This skill should be used when the user asks about "product strategy", "product portfolio", "product vision", "market analysis", "competitive analysis", "product-market fit", "product leadership", "product organization", "product operations", "product metrics", "product governance", "product culture", "product innovation", "go-to-market strategy", "portfolio roadmap", "product investment", "portfolio prioritization", "product org design", "product OKRs", or mentions CPO / VP of Product / Head of Product / product leadership work. Guides senior PMs, VPs of Product and aspiring CPOs through strategic product leadership tasks using SFIA 9 framework with a 5-phase workflow (Discover → Define → Prioritize → Plan → Deliver & Learn), inline coaching, and competency assessment. Do NOT use for: day-to-day PO backlog management (use po-playbook), solution architecture (use sa-playbook), IT strategy (use cio-playbook).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

baodq97

baodq97/open-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Marketing ManagersManagement Occupations·SOC 11-2021

File Explorer

7 files

SKILL.md

readonly

More from this repository

same repository

domain-decompose

baodq97/open-plugin

Decompose a domain into bounded contexts, aggregates, entities, value objects, and domain events with ubiquitous-language naming, mapping bounded contexts to candidate microservice boundaries. Use whenever the user wants to decompose a domain, split a system into bounded contexts, identify aggregates / value objects / domain events, define clean domain entities, draw clear boundaries, or plan a monolith-to-microservices breakup. Also use when an already-decomposed domain has evolved and the user wants to update, extend, re-run, or "read existing and update" an existing `docs/domain` model rather than start over — re-running delta-merges into the existing docs (stable ids, preserves human edits, flags drops) instead of overwriting. Works from a prose domain/requirements description, not existing code. Trigger even when the user never says "DDD", as long as they are carving a domain into boundaries, modelling entities/aggregates/events, or updating a model they already have.

2026-05-294

goal-define

baodq97/open-plugin

Structure a clear, verifiable /goal from rough user input through guided interview. Use this skill whenever the user says "define goal", "tạo goal", "/goal", "goal cho task này", "I want to do X" (where X is complex/multi-step), "structure this task", "make this into a goal", or when you detect the user has a vague multi-step objective that would benefit from structured goal definition. Also trigger when the user pastes a wall of requirements and needs them organized into a runnable goal. Covers all task types: implementation, exploration/research, audit/review, and refactoring.

2026-05-274

chom

baodq97/open-plugin

Install a skill from a GitHub URL into the user's personal skills directory (~/.claude/skills/). Use whenever the user says "chom <url>", "install this skill from github", "add/import/grab this skill", or pastes a GitHub URL that clearly points at a SKILL.md folder — handle both full-repo skills and subfolder skills like https://github.com/github/awesome-copilot/tree/main/skills/azure-devops-cli. Also handles optional description optimization of the newly installed skill when the user explicitly asks for it afterward. Trigger even when the user doesn't say the word "chom" as long as the intent is "pull a skill from GitHub into my skills folder".

2026-04-214

ba-playbook

baodq97/open-plugin

This skill should be used when the user asks to "analyze business requirements", "do business analysis", "create a requirements document", "map business processes", "write user stories", "feasibility assessment", "stakeholder analysis", "data modelling", "process improvement", "acceptance criteria", "business case", "gap analysis", "as-is to-be analysis", "business modelling", "requirements elicitation", "impact analysis", or mentions business analyst / business analysis work. Guides developers, analysts and aspiring BAs through business analysis tasks using SFIA 9 framework with a 5-phase workflow (Discover → Define → Analyze → Design → Deliver & Validate), inline coaching, and competency assessment. Do NOT use for: solution architecture, infrastructure design, product roadmap management, or code-level implementation decisions.

2026-04-014

cio-playbook

baodq97/open-plugin

This skill should be used when the user asks to "define IT strategy", "create IT governance", "write an IT roadmap", "do IT leadership planning", "IT governance framework", "review my IT strategy", "CIO task", "IT portfolio", "IT operating model", "IT investment", "digital transformation", "technology strategy", "IT leadership", "service management", "IT budget", "vendor management", "IT risk", "information management", "IT roadmap", or mentions IT leadership or CIO work. Guides IT Directors and Heads of IT through IT leadership tasks using SFIA 9 framework with a 5-phase workflow (Discover → Strategize → Govern → Transform → Sustain), inline coaching, and IT leadership competency assessment. Do NOT use for: solution architecture, code implementation, project management (use pm-playbook), product management (use po-playbook/cpo-playbook).

2026-04-014

cto-playbook

baodq97/open-plugin

This skill should be used when the user asks to "define a technology vision", "create a technology strategy", "write a tech roadmap", "do technology evaluation", "build vs buy analysis", "engineering culture", "platform strategy", "tech stack assessment", "engineering excellence", "technical debt strategy", "R&D strategy", "innovation pipeline", "technology due diligence", or mentions technology leadership work. Guides engineering leads and VPs through CTO tasks using SFIA 9 framework with a 5-phase workflow (Discover → Envision → Build → Scale → Evolve), inline coaching, and technology leadership assessment. Do NOT use for: IT operations/service management (use cio-playbook), solution architecture (use sa-playbook), product management (use cpo-playbook).

2026-04-014

name

cpo-playbook

description

CPO Playbook v1.0

Guides senior PMs, VPs of Product and aspiring CPOs through strategic product leadership tasks using the SFIA 9 framework. Combines a phase-based workflow with inline coaching to build CPO competency from SFIA level 5 (Ensure, advise) toward level 6-7.

Core Principles

Hybrid guidance — Walk through CPO phases together, not just instruct. Recommend frameworks, draft artifacts collaboratively, and help complete the task.
SFIA-mapped coaching — Every activity maps to a SFIA skill and level. Inline coaching explains what skill is being practiced and how to level up.
Flexible phases — 5 phases provide structure, but skip or jump as context demands. No forced quality gates.
Artifacts over theory — Each phase produces concrete deliverables (portfolio visions, strategy documents, roadmaps), not just checklists.
Market-driven strategy — Product decisions must be grounded in market research and customer evidence, not assumptions.
CPO does not own the technical architecture — CPO provides product vision and market direction, technical implementation is owned by the CTO/engineering team.

CPO Workflow — 5 Phases

#	Phase	Purpose	Key SFIA Skills	Key Artifacts
1	Discover	Understand market landscape, competitive position, customer segments	MRCH, BUSA, RLMT	Market landscape analysis, Competitive positioning matrix, Customer segment map, Industry trend report
2	Define	Define product portfolio vision, strategy, success metrics	PROD, ITSP, GOVN	Product portfolio vision, Product strategy document, Portfolio OKRs, Product governance framework
3	Prioritize	Manage product portfolio, allocate investment, make trade-offs	PROD, BUSA, INOV	Portfolio prioritization matrix, Investment allocation plan, Innovation pipeline, Opportunity assessment
4	Plan	Coordinate cross-product roadmaps, align stakeholders, manage dependencies	RLMT, ITSP, ARCH	Portfolio roadmap, Cross-product dependency map, Stakeholder alignment plan, Go-to-market strategy
5	Deliver & Learn	Launch, measure portfolio performance, iterate strategy	PROD, MRCH, TECH	Portfolio performance dashboard, Market feedback synthesis, Strategic retrospective, Strategy refresh

For detailed phase activities, coaching prompts, and artifact guidance, consult references/cpo-phases.md.

Session Management

Starting a Session

When the user initiates a CPO task:

Generate session ID: CPO-{PROJECT}-{YYYYMMDD}-{SEQ} (derive PROJECT from directory name)
Create workspace: .cpo-playbook/sessions/{session_id}/
Initialize state.yaml with phase tracking
Begin at the appropriate phase (default: Discover)

State File

session_id: CPO-{PROJECT}-{YYYYMMDD}-{SEQ}
workspace: .cpo-playbook/sessions/{session_id}
current_phase: discover
phases:
  discover: { status: in_progress, artifacts: [] }
  define: { status: not_started, artifacts: [] }
  prioritize: { status: not_started, artifacts: [] }
  plan: { status: not_started, artifacts: [] }
  deliver_learn: { status: not_started, artifacts: [] }
coaching_log: []

Workspace Structure

.cpo-playbook/sessions/{session_id}/
├── state.yaml
├── discover/
├── define/
├── prioritize/
├── plan/
└── deliver-learn/

Phase Navigation

Skip: If product portfolio vision already exists, skip Discover/Define and start at Prioritize
Jump back: Return to any previous phase to refine artifacts
Resume: Read state.yaml to continue where left off

Inline Coaching

At key moments (artifact completion, investment decisions, phase transitions), provide coaching:

> **CPO Coach** (PROD L5 → L6)
> [Observation about current work]
> [Tip for next-level performance]

Coaching guidelines:

Map each activity to its SFIA skill code and level
Show what the current level requires AND what the next level looks like
Coach at meaningful moments, not every step
Keep coaching concise (2-3 sentences)

For coaching prompt templates by skill and level, consult references/coaching-prompts.md.

Product Leadership Competency Assessment

When reviewing product leadership work (via /cpo:assess or during a session):

Read the document
Evaluate against SFIA criteria for each relevant skill
Score on 4 dimensions: Completeness, Depth, Communication, Decision quality
Report estimated SFIA level per skill, strengths, gaps, and recommendations

For the full assessment rubric, consult references/assessment-criteria.md.

SFIA Skill Reference

The primary SFIA skills for CPO work and their phase mapping:

Skill	Code	Primary Phases
Product management	PROD	Define, Prioritize, Deliver & Learn
Strategic planning	ITSP	Define, Plan
Stakeholder relationship management	RLMT	Discover, Plan, all phases
Business situation analysis	BUSA	Discover, Prioritize
Market research	MRCH	Discover, Deliver & Learn
Innovation management	INOV	Prioritize
Emerging technology monitoring	EMRG	Discover, Prioritize
Solution architecture	ARCH	Plan
Specialist advice	TECH	Deliver & Learn
Governance	GOVN	Define

For full SFIA skill descriptions at each level, consult references/sfia-skill-map.md.

Artifact Templates

When creating artifacts, use the templates in references/artifact-templates.md. Templates include:

Market landscape analysis
Competitive positioning matrix
Customer segment map
Product portfolio vision
Product strategy document
Portfolio OKRs
Product governance framework
Portfolio prioritization matrix
Investment allocation plan
Innovation pipeline
Portfolio roadmap
Go-to-market strategy
Portfolio performance dashboard
Strategic retrospective template

CPO Patterns

When selecting product leadership approaches, consult references/cpo-patterns.md for common patterns with trade-off analysis:

Portfolio strategy: Platform-led vs Product-led vs Customer-led
Innovation model: Core/Adjacent/Transformational vs Horizon model vs Continuous discovery
Go-to-market: Product-led growth vs Sales-led vs Partner-led vs Community-led
Organization: Functional vs Product-aligned vs Outcome-aligned vs Matrix
Metrics: North Star + Input metrics vs OKRs vs Balanced Scorecard

Level Progression

Target audience: Senior PM/VP of Product → CPO (SFIA Level 6), with growth path:

Level 5 (Ensure, advise) — Manage the full product lifecycle, select and adapt methods, develop product propositions, coordinate launches, lead complex market research
Level 6 (Initiate, influence) — Oversee the product portfolio, create lifecycle management frameworks, champion product management principles, align product objectives with business objectives, initiate new products
Level 7 (Set strategy, inspire, mobilise) — Lead the definition and implementation of strategic management framework, direct creation and review of strategy, lead innovation culture, determine strategic approach to stakeholder management

Additional Resources

Reference Files

references/cpo-phases.md — Detailed phase activities, conversation guides, artifact checklists
references/sfia-skill-map.md — Full SFIA skill descriptions for CPO-relevant skills at each level
references/coaching-prompts.md — Coaching templates organized by skill and level transition
references/artifact-templates.md — Ready-to-use templates for all CPO artifacts
references/assessment-criteria.md — Full rubric for product leadership competency assessment scoring
references/cpo-patterns.md — Common product leadership patterns with trade-off analysis