pm/strategic-review

Evaluates business value of features using five-dimension strategic scoring framework.

553|50|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/echoVic/boss-skill --skill pm-strategic-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm/strategic-review
Source: https://github.com/echoVic/boss-skill/tree/main/skill/skills/pm/strategic-review
Command: npx skills add https://github.com/echoVic/boss-skill --skill pm-strategic-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to decide whether a feature or project is worth investing in, relying on gut feeling rather than structured evidence. This Skill provides a CEO-level strategic review methodology that scores market fit, ROI, competitive advantage, risk, and strategic alignment to produce a defensible go/no-go decision.

Core Features & Use Cases

  • Five-Dimension Scoring: Evaluates market fit (30%), ROI (25%), competitive advantage (20%), risk (15%), and strategic alignment (10%) with weighted scoring from 1-5.
  • Decision Mapping: Maps composite scores to clear decisions: proceed (≥4.0), adjust (3.0-3.9), or defer (<3.0).
  • Structured Output: Generates a strategic-review.md report under .boss/<feature>/ containing an executive summary, risk matrix, strategic recommendations, and key assumptions.
  • Use Case: Before committing engineering resources to a new feature, run a strategic review to quantify market opportunity, estimate payback period, assess competitive moats, and document risks for stakeholder communication.

Quick Start

Ask the agent to run a strategic review on your proposed feature to evaluate its market fit, ROI, competitive advantage, risks, and strategic alignment.

Frequently Asked Questions about pm/strategic-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether a product feature is worth building?

Use a weighted scoring framework that rates market fit, ROI, competitive advantage, risk, and strategic alignment on a 1-5 scale. Composite scores above 4.0 indicate proceed, 3.0-3.9 indicate adjust the approach, and below 3.0 indicate defer investment.

What dimensions should a strategic product review cover?

A strategic review should cover five dimensions: market fit (TAM/SAM/SOM and pain intensity), ROI (cost, revenue model, payback period), competitive advantage (moats and switching costs), risk assessment, and alignment with company strategy.

How is a strategic review different from a technical code review?

A strategic review evaluates whether to build something and why, focusing on business value, market opportunity, and ROI. A technical review evaluates implementation quality, focusing on code correctness, architecture, and engineering practices.

When should I run a strategic review instead of going straight to development?

Run a strategic review before committing resources to new features, when prioritizing under resource constraints, when product direction is disputed, or when preparing materials for investors and stakeholders.

What output does the strategic review produce?

It generates a strategic-review.md file under .boss/<feature>/ containing an executive summary with value rating, five-dimension scoring details, a risk matrix with mitigations, strategic recommendations, and key assumptions with validation status.