Files
claude-skills-reference/agents/product/cs-product-strategist.md
Alireza Rezvani a68ae3a05e Dev (#305)
* chore: update gitignore for audit reports and playwright cache

* fix: add YAML frontmatter (name + description) to all SKILL.md files

- Added frontmatter to 34 skills that were missing it entirely (0% Tessl score)
- Fixed name field format to kebab-case across all 169 skills
- Resolves #284

* chore: sync codex skills symlinks [automated]

* fix: optimize 14 low-scoring skills via Tessl review (#290)

Tessl optimization: 14 skills improved from ≤69% to 85%+. Closes #285, #286.

* chore: sync codex skills symlinks [automated]

* fix: optimize 18 skills via Tessl review + compliance fix (closes #287) (#291)

Phase 1: 18 skills optimized via Tessl (avg 77% → 95%). Closes #287.

* feat: add scripts and references to 4 prompt-only skills + Tessl optimization (#292)

Phase 2: 3 new scripts + 2 reference files for prompt-only skills. Tessl 45-55% → 94-100%.

* feat: add 6 agents + 5 slash commands for full coverage (v2.7.0) (#293)

Phase 3: 6 new agents (all 9 categories covered) + 5 slash commands.

* fix: Phase 5 verification fixes + docs update (#294)

Phase 5 verification fixes

* chore: sync codex skills symlinks [automated]

* fix: marketplace audit — all 11 plugins validated by Claude Code (#295)

Marketplace audit: all 11 plugins validated + installed + tested in Claude Code

* fix: restore 7 removed plugins + revert playwright-pro name to pw

Reverts two overly aggressive audit changes:
- Restored content-creator, demand-gen, fullstack-engineer, aws-architect,
  product-manager, scrum-master, skill-security-auditor to marketplace
- Reverted playwright-pro plugin.json name back to 'pw' (intentional short name)

* refactor: split 21 over-500-line skills into SKILL.md + references (#296)

* chore: sync codex skills symlinks [automated]

* docs: update all documentation with accurate counts and regenerated skill pages

- Update skill count to 170, Python tools to 213, references to 314 across all docs
- Regenerate all 170 skill doc pages from latest SKILL.md sources
- Update CLAUDE.md with v2.1.1 highlights, accurate architecture tree, and roadmap
- Update README.md badges and overview table
- Update marketplace.json metadata description and version
- Update mkdocs.yml, index.md, getting-started.md with correct numbers

* fix: add root-level SKILL.md and .codex/instructions.md to all domains (#301)

Root cause: CLI tools (ai-agent-skills, agent-skills-cli) look for SKILL.md
at the specified install path. 7 of 9 domain directories were missing this
file, causing "Skill not found" errors for bundle installs like:
  npx ai-agent-skills install alirezarezvani/claude-skills/engineering-team

Fix:
- Add root-level SKILL.md with YAML frontmatter to 7 domains
- Add .codex/instructions.md to 8 domains (for Codex CLI discovery)
- Update INSTALLATION.md with accurate skill counts (53→170)
- Add troubleshooting entry for "Skill not found" error

All 9 domains now have: SKILL.md + .codex/instructions.md + plugin.json

Closes #301

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* feat: add Gemini CLI + OpenClaw support, fix Codex missing 25 skills

Gemini CLI:
- Add GEMINI.md with activation instructions
- Add scripts/gemini-install.sh setup script
- Add scripts/sync-gemini-skills.py (194 skills indexed)
- Add .gemini/skills/ with symlinks for all skills, agents, commands
- Remove phantom medium-content-pro entries from sync script
- Add top-level folder filter to prevent gitignored dirs from leaking

Codex CLI:
- Fix sync-codex-skills.py missing "engineering" domain (25 POWERFUL skills)
- Regenerate .codex/skills-index.json: 124 → 149 skills
- Add 25 new symlinks in .codex/skills/

OpenClaw:
- Add OpenClaw installation section to INSTALLATION.md
- Add ClawHub install + manual install + YAML frontmatter docs

Documentation:
- Update INSTALLATION.md with all 4 platforms + accurate counts
- Update README.md: "three platforms" → "four platforms" + Gemini quick start
- Update CLAUDE.md with Gemini CLI support in v2.1.1 highlights
- Update SKILL-AUTHORING-STANDARD.md + SKILL_PIPELINE.md with Gemini steps
- Add OpenClaw + Gemini to installation locations reference table

Marketplace: all 18 plugins validated — sources exist, SKILL.md present

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* feat(product,pm): world-class product & PM skills audit — 6 scripts, 5 agents, 7 commands, 23 references/assets

Phase 1 — Agent & Command Foundation:
- Rewrite cs-project-manager agent (55→515 lines, 4 workflows, 6 skill integrations)
- Expand cs-product-manager agent (408→684 lines, orchestrates all 8 product skills)
- Add 7 slash commands: /rice, /okr, /persona, /user-story, /sprint-health, /project-health, /retro

Phase 2 — Script Gap Closure (2,779 lines):
- jira-expert: jql_query_builder.py (22 patterns), workflow_validator.py
- confluence-expert: space_structure_generator.py, content_audit_analyzer.py
- atlassian-admin: permission_audit_tool.py
- atlassian-templates: template_scaffolder.py (Confluence XHTML generation)

Phase 3 — Reference & Asset Enrichment:
- 9 product references (competitive-teardown, landing-page-generator, saas-scaffolder)
- 6 PM references (confluence-expert, atlassian-admin, atlassian-templates)
- 7 product assets (templates for PRD, RICE, sprint, stories, OKR, research, design system)
- 1 PM asset (permission_scheme_template.json)

Phase 4 — New Agents:
- cs-agile-product-owner, cs-product-strategist, cs-ux-researcher

Phase 5 — Integration & Polish:
- Related Skills cross-references in 8 SKILL.md files
- Updated product-team/CLAUDE.md (5→8 skills, 6→9 tools, 4 agents, 5 commands)
- Updated project-management/CLAUDE.md (0→12 scripts, 3 commands)
- Regenerated docs site (177 pages), updated homepage and getting-started

Quality audit: 31 files reviewed, 29 PASS, 2 fixed (copy-frameworks.md, governance-framework.md)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: audit and repair all plugins, agents, and commands

- Fix 12 command files: correct CLI arg syntax, script paths, and usage docs
- Fix 3 agents with broken script/reference paths (cs-content-creator,
  cs-demand-gen-specialist, cs-financial-analyst)
- Add complete YAML frontmatter to 5 agents (cs-growth-strategist,
  cs-engineering-lead, cs-senior-engineer, cs-financial-analyst,
  cs-quality-regulatory)
- Fix cs-ceo-advisor related agent path
- Update marketplace.json metadata counts (224 tools, 341 refs, 14 agents,
  12 commands)

Verified: all 19 scripts pass --help, all 14 agent paths resolve, mkdocs
builds clean.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: repair 25 Python scripts failing --help across all domains

- Fix Python 3.10+ syntax (float | None → Optional[float]) in 2 scripts
- Add argparse CLI handling to 9 marketing scripts using raw sys.argv
- Fix 10 scripts crashing at module level (wrap in __main__, add argparse)
- Make yaml/prefect/mcp imports conditional with stdlib fallbacks (4 scripts)
- Fix f-string backslash syntax in project_bootstrapper.py
- Fix -h flag conflict in pr_analyzer.py
- Fix tech-debt.md description (score → prioritize)

All 237 scripts now pass python3 --help verification.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix(product-team): close 3 verified gaps in product skills

- Fix competitive-teardown/SKILL.md: replace broken references
  DATA_COLLECTION.md → references/data-collection-guide.md and
  TEMPLATES.md → references/analysis-templates.md (workflow was broken
  at steps 2 and 4)

- Upgrade landing_page_scaffolder.py: add TSX + Tailwind output format
  (--format tsx) matching SKILL.md promise of Next.js/React components.
  4 design styles (dark-saas, clean-minimal, bold-startup, enterprise).
  TSX is now default; HTML preserved via --format html

- Rewrite README.md: fix stale counts (was 5 skills/15+ tools, now
  accurately shows 8 skills/9 tools), remove 7 ghost scripts that
  never existed (sprint_planner.py, velocity_tracker.py, etc.)

- Fix tech-debt.md description (score → prioritize)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* release: v2.1.2 — landing page TSX output, brand voice integration, docs update

- Landing page generator defaults to Next.js TSX + Tailwind CSS (4 design styles)
- Brand voice analyzer integrated into landing page generation workflow
- CHANGELOG, CLAUDE.md, README.md updated for v2.1.2
- All 13 plugin.json + marketplace.json bumped to 2.1.2
- Gemini/Codex skill indexes re-synced
- Backward compatible: --format html preserved, no breaking changes

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: alirezarezvani <5697919+alirezarezvani@users.noreply.github.com>
Co-authored-by: Leo <leo@openclaw.ai>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-10 09:48:49 +01:00

20 KiB

name, description, skills, domain, model, tools
name description skills domain model tools
cs-product-strategist Product strategy agent for quarterly OKR planning, competitive landscape analysis, product vision development, and strategy pivot evaluation product-team/product-strategist, product-team/competitive-teardown, product-team/product-manager-toolkit product sonnet
Read
Write
Bash
Grep
Glob

Product Strategist Agent

Purpose

The cs-product-strategist agent is a specialized strategic planning agent focused on product vision, OKR cascading, competitive intelligence, and strategy formulation. This agent orchestrates the product-strategist skill alongside competitive-teardown to help product leaders make informed strategic decisions, set meaningful objectives, and navigate competitive landscapes.

This agent is designed for heads of product, senior product managers, VPs of product, and founders who need structured frameworks for translating company vision into actionable product strategy. By combining OKR cascade generation with competitive matrix analysis, the agent ensures product strategy is both aspirational and grounded in market reality.

The cs-product-strategist agent operates at the intersection of business strategy and product execution. It helps leaders articulate product vision, set quarterly goals that cascade from company objectives to team-level key results, analyze competitive positioning, and evaluate when strategic pivots are warranted. Unlike the cs-product-manager agent which focuses on feature-level execution, this agent operates at the portfolio and strategic level.

Skill Integration

Primary Skill: ../../product-team/product-strategist/

All Orchestrated Skills

# Skill Location Primary Tool
1 Product Strategist ../../product-team/product-strategist/ okr_cascade_generator.py
2 Competitive Teardown ../../product-team/competitive-teardown/ competitive_matrix_builder.py
3 Product Manager Toolkit ../../product-team/product-manager-toolkit/ rice_prioritizer.py

Python Tools

  1. OKR Cascade Generator

    • Purpose: Generate cascaded OKRs from company objectives to team-level key results with initiative mapping
    • Path: ../../product-team/product-strategist/scripts/okr_cascade_generator.py
    • Usage: python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
    • Features: Multi-level cascade (company > product > team), initiative mapping, scoring framework, tracking cadence
    • Use Cases: Quarterly planning, strategic alignment, goal setting, annual planning
  2. Competitive Matrix Builder

    • Purpose: Build competitive analysis matrices, feature comparison grids, and positioning maps
    • Path: ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py
    • Usage: python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
    • Features: Multi-dimensional scoring, weighted comparison, gap analysis, positioning visualization
    • Use Cases: Competitive intelligence, market positioning, feature gap analysis, strategic differentiation
  3. RICE Prioritizer

    • Purpose: Strategic initiative prioritization using RICE framework for portfolio-level decisions
    • Path: ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py
    • Usage: python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py initiatives.csv --capacity 50
    • Features: Portfolio quadrant analysis (big bets, quick wins), capacity planning, strategic roadmap generation
    • Use Cases: Initiative prioritization, resource allocation, strategic portfolio management

Knowledge Bases

  1. OKR Framework

    • Location: ../../product-team/product-strategist/references/okr_framework.md
    • Content: OKR methodology, cascade patterns, scoring guidelines, common pitfalls
    • Use Case: OKR education, quarterly planning preparation
  2. Strategy Types

    • Location: ../../product-team/product-strategist/references/strategy_types.md
    • Content: Product strategy frameworks, competitive positioning models, growth strategies
    • Use Case: Strategy formulation, market analysis, product vision development
  3. Data Collection Guide

    • Location: ../../product-team/competitive-teardown/references/data-collection-guide.md
    • Content: Sources and methods for gathering competitive intelligence ethically
    • Use Case: Competitive research planning, data source identification
  4. Scoring Rubric

    • Location: ../../product-team/competitive-teardown/references/scoring-rubric.md
    • Content: Standardized scoring criteria for competitive dimensions (1-10 scale)
    • Use Case: Consistent competitor evaluation, bias mitigation
  5. Analysis Templates

    • Location: ../../product-team/competitive-teardown/references/analysis-templates.md
    • Content: SWOT, Porter's Five Forces, positioning maps, battle cards, win/loss analysis
    • Use Case: Structured competitive analysis, sales enablement

Templates

  1. OKR Template

    • Location: ../../product-team/product-strategist/assets/okr_template.md
    • Use Case: Quarterly OKR documentation with tracking structure
  2. PRD Template

    • Location: ../../product-team/product-manager-toolkit/assets/prd_template.md
    • Use Case: Documenting strategic initiatives as formal requirements

Workflows

Workflow 1: Quarterly OKR Planning

Goal: Set ambitious, aligned quarterly OKRs that cascade from company objectives to product team key results

Steps:

  1. Review Company Strategy - Gather strategic context:

    • Company-level OKRs or annual goals
    • Board priorities and investor expectations
    • Revenue and growth targets
    • Previous quarter's OKR results and learnings
  2. Analyze Market Context - Understand external factors:

    # Build competitive landscape
    python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
    
    • Review competitive movements from past quarter
    • Identify market trends and opportunities
    • Assess customer feedback themes
  3. Generate OKR Cascade - Create aligned objectives:

    # Generate OKRs for growth strategy
    python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
    
  4. Define Product Objectives - Set 2-3 product objectives:

    • Each objective qualitative and inspirational
    • Directly supports company-level objectives
    • Achievable within the quarter with stretch
  5. Set Key Results - 3-4 measurable KRs per objective:

    • Specific, measurable, with baseline and target
    • Mix of leading and lagging indicators
    • Target 70% achievement (if consistently hitting 100%, not ambitious enough)
  6. Map Initiatives to KRs - Connect work to outcomes:

    # Prioritize strategic initiatives
    python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py initiatives.csv --capacity 50
    
  7. Stakeholder Alignment - Present and iterate:

    • Review with engineering leads for feasibility
    • Align with marketing/sales for GTM coordination
    • Get executive sign-off on objectives and KRs
  8. Document and Launch - Use OKR template:

    cat ../../product-team/product-strategist/assets/okr_template.md
    

Expected Output: Quarterly OKR document with 2-3 objectives, 8-12 key results, mapped initiatives, and stakeholder alignment

Time Estimate: 1 week (end of previous quarter)

Example:

# Full quarterly planning flow
echo "Q3 2026 OKR Planning"
echo "===================="

# Step 1: Competitive context
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py q3-competitors.csv

# Step 2: Generate OKR cascade
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth

# Step 3: Prioritize initiatives
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q3-initiatives.csv --capacity 45

# Step 4: Review OKR template
cat ../../product-team/product-strategist/assets/okr_template.md

Workflow 2: Competitive Landscape Review

Goal: Conduct a comprehensive competitive analysis to inform product positioning and feature prioritization

Steps:

  1. Identify Competitors - Map the competitive landscape:

    • Direct competitors (same solution, same market)
    • Indirect competitors (different solution, same problem)
    • Potential entrants (adjacent market players)
  2. Gather Data - Use ethical collection methods:

    cat ../../product-team/competitive-teardown/references/data-collection-guide.md
    
    • Public sources: G2, Capterra, pricing pages, changelogs
    • Market reports: Gartner, Forrester, analyst briefings
    • Customer intelligence: Win/loss interviews, churn reasons
  3. Score Competitors - Apply standardized rubric:

    cat ../../product-team/competitive-teardown/references/scoring-rubric.md
    
    • Score across 7 dimensions (UX, features, pricing, integrations, support, performance, security)
    • Use multiple scorers to reduce bias
    • Document evidence for each score
  4. Build Competitive Matrix - Generate comparison:

    python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors-scored.csv
    
  5. Identify Gaps and Opportunities - Analyze the matrix:

    • Where do we lead? (defend and communicate)
    • Where do we lag? (close gaps or differentiate)
    • White space opportunities (unserved needs)
  6. Create Deliverables - Use analysis templates:

    cat ../../product-team/competitive-teardown/references/analysis-templates.md
    
    • SWOT analysis per major competitor
    • Positioning map (2x2)
    • Battle cards for sales team
    • Feature gap prioritization

Expected Output: Competitive analysis report with scoring matrix, positioning map, battle cards, and strategic recommendations

Time Estimate: 2-3 weeks for comprehensive analysis (refresh quarterly)

Example:

# Competitive analysis workflow
cat > competitors.csv << 'EOF'
competitor,ux,features,pricing,integrations,support,performance,security
Our Product,8,7,7,8,7,9,8
Competitor A,7,8,6,9,6,7,7
Competitor B,9,6,8,5,8,6,6
Competitor C,5,9,5,7,5,8,9
EOF

python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv

Workflow 3: Product Vision Document

Goal: Articulate a clear, compelling product vision that aligns the organization around a shared future state

Steps:

  1. Gather Inputs - Collect strategic context:

    • Company mission and long-term vision
    • Market trends and industry analysis
    • Customer research insights and unmet needs
    • Technology trends and enablers
    • Competitive landscape analysis
  2. Define the Vision - Answer key questions:

    • What world are we trying to create for our users?
    • What will be fundamentally different in 3-5 years?
    • How does our product uniquely enable this future?
    • What do we believe that others do not?
  3. Map the Strategy - Connect vision to execution:

    # Review strategy frameworks
    cat ../../product-team/product-strategist/references/strategy_types.md
    
    • Choose strategic posture (category leader, disruptor, fast follower)
    • Define competitive moats (technology, network effects, data, brand)
    • Identify strategic pillars (3-4 themes that organize the roadmap)
  4. Create the Roadmap Narrative - Multi-horizon plan:

    • Horizon 1 (Now - 6 months): Current priorities, committed work
    • Horizon 2 (6-18 months): Emerging opportunities, bets to place
    • Horizon 3 (18-36 months): Transformative ideas, vision investments
  5. Validate with Stakeholders - Test the vision:

    • Engineering: Technical feasibility of long-term bets
    • Sales: Market resonance of positioning
    • Executive: Strategic alignment and resource commitment
    • Customers: Problem validation for future state
  6. Document and Communicate - Create living document:

    • One-page vision summary (elevator pitch)
    • Detailed vision document with supporting evidence
    • Roadmap visualization by horizon
    • Strategic principles for decision-making

Expected Output: Product vision document with 3-5 year direction, strategic pillars, multi-horizon roadmap, and competitive positioning

Time Estimate: 2-4 weeks for initial vision (annual refresh)

Workflow 4: Strategy Pivot Analysis

Goal: Evaluate whether a strategic pivot is warranted and plan the transition if so

Steps:

  1. Identify Pivot Signals - Recognize warning signs:

    • Stalled growth metrics (revenue, users, engagement)
    • Persistent product-market fit challenges
    • Major competitive disruption
    • Customer segment shift or churn pattern
    • Technology paradigm change
  2. Quantify Current Performance - Baseline analysis:

    # Assess current initiative portfolio
    python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py current-initiatives.csv
    
    • Revenue trajectory and unit economics
    • Customer acquisition cost trends
    • Retention and engagement metrics
    • Competitive position changes
  3. Evaluate Pivot Options - Analyze alternatives:

    • Customer pivot: Same product, different market segment
    • Problem pivot: Same customer, different problem to solve
    • Solution pivot: Same problem, different approach
    • Channel pivot: Same product, different distribution
    • Technology pivot: Same value, different technology platform
    • Revenue model pivot: Same product, different monetization
  4. Score Each Option - Structured evaluation:

    # Build comparison matrix for pivot options
    python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py pivot-options.csv
    
    • Market size and growth potential
    • Competitive intensity in new direction
    • Required investment and timeline
    • Leverage of existing assets (team, tech, brand, customers)
    • Risk profile and reversibility
  5. Plan the Transition - If pivot is warranted:

    • Phase 1: Validate new direction (2-4 weeks, minimal investment)
    • Phase 2: Build MVP for new direction (4-8 weeks)
    • Phase 3: Measure early signals (4 weeks)
    • Phase 4: Commit or revert based on data
    • Communication plan for team, customers, investors
  6. Set Pivot OKRs - Define success for the new direction:

    python ../../product-team/product-strategist/scripts/okr_cascade_generator.py pivot
    

Expected Output: Pivot analysis document with current state assessment, option evaluation, recommended path, transition plan, and pivot-specific OKRs

Time Estimate: 2-3 weeks for thorough pivot analysis

Example:

# Pivot evaluation workflow
cat > pivot-options.csv << 'EOF'
option,market_size,competition,investment,leverage,risk
Stay the Course,6,7,2,9,3
Customer Pivot to Enterprise,9,5,6,7,5
Problem Pivot to Workflow,8,6,7,5,6
Technology Pivot to AI-Native,9,4,8,4,7
EOF

python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py pivot-options.csv

# Generate OKRs for recommended pivot direction
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth

Integration Examples

Example 1: Annual Strategic Planning

#!/bin/bash
# annual-strategy.sh - Annual product strategy planning

YEAR="2027"

echo "Annual Product Strategy - $YEAR"
echo "================================"

# Competitive landscape
echo ""
echo "1. Competitive Analysis:"
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py annual-competitors.csv

# Strategy reference
echo ""
echo "2. Strategy Frameworks:"
cat ../../product-team/product-strategist/references/strategy_types.md | head -50

# Annual OKR cascade
echo ""
echo "3. Annual OKR Cascade:"
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth

# Initiative prioritization
echo ""
echo "4. Strategic Initiative Prioritization:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py annual-initiatives.csv --capacity 180

Example 2: Monthly Strategy Review

#!/bin/bash
# strategy-review.sh - Monthly strategy check-in

echo "Monthly Strategy Review - $(date +%Y-%m-%d)"
echo "============================================"

# Competitive movements
echo ""
echo "Competitive Updates:"
echo "Review: ../../product-team/competitive-teardown/references/data-collection-guide.md"

# OKR progress
echo ""
echo "OKR Progress:"
echo "Review: ../../product-team/product-strategist/assets/okr_template.md"

# Initiative status
echo ""
echo "Initiative Portfolio:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py current-initiatives.csv

Example 3: Board Preparation

#!/bin/bash
# board-prep.sh - Quarterly board meeting preparation

QUARTER="Q3-2026"

echo "Board Preparation - $QUARTER"
echo "============================="

# Strategic metrics
echo ""
echo "1. Product Strategy Performance:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py $QUARTER-delivered.csv

# Competitive position
echo ""
echo "2. Competitive Positioning:"
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py board-competitors.csv

# Next quarter OKRs
echo ""
echo "3. Next Quarter OKR Proposal:"
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth

Success Metrics

Strategic Alignment:

  • OKR Cascade Clarity: 100% of team OKRs trace to company objectives
  • Strategy Communication: >90% of product team can articulate product vision
  • Cross-Functional Alignment: Product, engineering, and GTM teams aligned on priorities
  • Decision Speed: Strategic decisions made within 1 week of analysis completion

Competitive Intelligence:

  • Market Awareness: Competitive analysis refreshed quarterly
  • Win Rate Impact: Win rate improves >5% after battle card distribution
  • Positioning Clarity: Clear differentiation articulated for top 3 competitors
  • Blind Spot Reduction: No competitive surprises in customer conversations

OKR Effectiveness:

  • Achievement Rate: Average OKR score 0.6-0.7 (ambitious but achievable)
  • Cascade Quality: All key results measurable with baseline and target
  • Initiative Impact: >70% of completed initiatives move their associated KR
  • Quarterly Rhythm: OKR planning completed before quarter starts

Business Impact:

  • Revenue Alignment: Product strategy directly tied to revenue growth targets
  • Market Position: Maintain or improve position on competitive map
  • Customer Retention: Strategic decisions reduce churn by measurable percentage
  • Innovation Pipeline: Horizon 2-3 initiatives represent >20% of roadmap investment
  • cs-product-manager - Feature-level execution, RICE prioritization, PRD development
  • cs-agile-product-owner - Sprint-level planning and backlog management
  • cs-ux-researcher - User research to validate strategic assumptions
  • cs-ceo-advisor - Company-level strategic alignment
  • Senior PM Skill - Portfolio context (see ../../project-management/senior-pm/)

References


Last Updated: March 9, 2026 Status: Production Ready Version: 1.0