AgentSkillsCN

Product Strategy Review

运用 PRISM 框架,结合愿景评分、OKR 对弈与团队架构指导,全面审视产品战略、愿景与 OKR。

SKILL.md
--- frontmatter
name: Product Strategy Review
description: >
  Review product strategy, vision, and OKRs using the PRISM framework,
  vision scoring, OKR sparring, and team structure guidance.

Product Strategy Review

This skill provides four review modes for product strategy artifacts:

  1. PRISM Strategy Review - Full evidence-based self-review of strategy documents. See references/prism-strategy-review.md.
  2. Product Vision Review - Score vision documents against 4 criteria. See references/product-vision-review.md.
  3. OKR Sparring Partner - Sharp, practical OKR coaching. See references/okr-sparring-partner.md.
  4. Team Structure Guidance - Org design models and principles. See references/team-structure-guide.md.

PRISM Strategy Review

Intent

Help a Head of Product/CPO conduct evidence-based self-review of their strategy document to validate: (1) Core Thesis, (2) Strategic Options comparison, (3) Capital Allocation decisions, (4) Pre-mortem/Kill-Switch and Adaptation definition, (5) Mission/Vision alignment and Stakeholder alignment.

Outputs

  • review.md (human-readable, <= 900 words)
  • review.json (machine-readable)

How to use (fastest path)

  1. Run the Evidence Readiness auto-gate. If status = Hold, run a 1-day evidence sprint, then re-run the gate. Do not score while on Hold.
  2. If status = Proceed, score each PRISM dimension 0-5 using rubrics in references/prism-strategy-review.md. Capture concrete evidence citations.
  3. Record strengths, risks, decisions, and improvements using the Output Template.
  4. Compute Overall Score and decision. Assign owners and due dates for improvements.

PRISM Dimensions (0-5 each)

  • P - Problem Diagnosis
  • R - Reframe Opportunity
  • I - Intentional Bets
  • S - Systemized Execution
  • M - Momentum & Meta-Reflection

Overall Score = average (equal weighting).


Product Vision Review

Purpose

Review any attached or referenced Product Vision document. Evaluate its strength against proven principles and provide constructive feedback.

Process

  1. Parse the document.
  2. Run the Evidence Readiness Check (verify a vision statement, user problem, and time horizon exist).
  3. Score against the 4 Vision Criteria (0-5 each): Lofty & Inspiring, Realistic & Attainable, Constraint-Free, Grounded in User Problem.
  4. Provide feedback using the Output Template in references/product-vision-review.md.

OKR Sparring Partner

Role

World-class OKR coach providing sharp and practical criticism like a boxing sparring partner for OKR drafts.

Analysis framework

  1. Objective clarity and strategic alignment
  2. Key Results outcome-centricity and measurement suitability
  3. Strategic/vision connection
  4. Assumption validation and causal relationship review
  5. Common pitfall check
  6. Expression clarity and restructuring
  7. Team capability and resource reality

For the complete framework, improvement templates, and diagnostic questions, see references/okr-sparring-partner.md.


Team Structure Guidance

Reference references/team-structure-guide.md for:

  • Functional, Matrix, Value Stream, and Divisional organization models
  • Re-org considerations and when to avoid restructuring
  • Common team structure patterns (Squad/Pod, Triad, Feature Teams, Outcome Teams)
  • Design principles for team structure

Inputs

For PRISM Strategy Review, the following are required:

  • doc_link (strategy document to review)
  • evidence_hub_link (consolidated evidence location)
  • product_or_area
  • owner
  • review_window_start and review_window_end (YYYY-MM-DD)
  • riskiest_assumptions (at least 2)

Optional: baseline_metric, north_star, capacity_window, runway_months.

If inputs are missing, return a MissingInputs list with a 1-Day Evidence Sprint proposal.

Citation Standard

All evidence must use this format: [[ev-id|path#line-range|YYYY-MM-DD]]

Example: [[ev-12|initiatives/kbo/analysis.md#L42-L77|2025-09-10]]

Missing citations result in a 1-step deduction per dimension.

Follow the writing standards in _shared/writing-standards.md for all outputs.