plan-ceo-review

Evaluate product plans for scope, user value, and strategic risks.

2|1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill plan-ceo-review-code-saurabh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/plan-ceo-review
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill plan-ceo-review-code-saurabh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from investing engineering effort in poorly scoped, low-value, or strategically weak product plans by evaluating them through a rigorous CEO and founder lens.

Core Features & Use Cases

  • Strategic Plan Review: Clarify the underlying user problem, primary user, 90-day success outcome, and proposed solution.
  • Scope Evaluation: Choose whether to expand, selectively expand, hold, or reduce scope based on user value, engineering cost, risk, and validation needs.
  • Competitive and Moat Analysis: Assess competitive exposure, durable advantages, business value, and whether the plan builds a feature or a defensible platform.
  • Structured Handoff: Produce success metrics, assumptions, risks, scope decisions, and strategic constraints for downstream engineering review.

Quick Start

Use the CEO review skill to evaluate this product plan, identify the right scope mode, assess its moat and competitive risks, and prepare the structured engineering handoff.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I stress-test a product strategy for market value before engineering begins?

To stress-test a product strategy before engineering, evaluate the underlying user problem, validate assumptions, assess competitive exposure, and define measurable success metrics. This process prevents misaligned scope and wasted engineering investment.

What is a competitive analysis and moat assessment for feature planning?

A competitive analysis and moat assessment evaluates competitive exposure and durable advantages to determine whether a plan builds a defensible platform or a standalone feature. It clarifies long-term business value and strategic impact.

How do I prepare a structured engineering handoff with scope decisions and risks?

To prepare a structured engineering handoff, document scope decisions, explicit tradeoff analysis, validated assumptions, identified risks, and strategic constraints. This provides downstream engineering teams with clear success metrics and boundaries.

When do I need to evaluate scope decisions for user value and engineering cost?

You need to evaluate scope decisions for user value and engineering cost during strategic reviews before development begins. This step determines whether to expand, hold, or reduce scope based on risk and validation needs.

What is the best way to define measurable success metrics for a 90-day product outcome?

The best way to define measurable success metrics for a 90-day product outcome is to clarify the primary user and establish explicit tradeoff analysis during strategic plan review. This ensures tracking aligns with strategic impact.

Why does a product plan require assumption validation and explicit tradeoff analysis?

A product plan requires assumption validation and explicit tradeoff analysis to prevent teams from investing engineering effort in poorly scoped or strategically weak features. This rigorous evaluation ensures durable business value.