plan-ceo-review

Evaluate product plans and recommend scope expansion, hold, or reduction.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/minfengyuan/harness-knowledge-base --skill plan-ceo-review-minfengyuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/minfengyuan/harness-knowledge-base/tree/main/skills/plan-ceo-review
Command: npx skills add https://github.com/minfengyuan/harness-knowledge-base --skill plan-ceo-review-minfengyuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide founder- or product-lead–level critique of a plan to challenge its premise, sharpen the product direction, and decide whether the scope should expand, contract, or be reframed before engineering work begins.

Core Features & Use Cases

  • Strategic Premise Challenge: Re-evaluates whether the plan solves a real user problem and whether the target user and wedge are sufficiently concrete.
  • Mode-Based Recommendations: Delivers one of four modes (scope expansion, selective expansion, hold scope, scope reduction) with explicit, decision-oriented guidance.
  • Structured Output: Produces a concise review with premise, scope assessment, risks, recommendation (selected mode), and a single next step to advance the plan.
  • Use Case: A founder asks whether a proposed v1 is too timid or overbuilt; use this skill to pick a mode and produce a concrete recommendation that trades off ambition, focus, and shipability.

Quick Start

Request a CEO-style review of this plan and a clear recommendation to expand, selectively expand, hold, or reduce the scope along with the single best next step.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I review a product plan to decide if the scope is too ambitious or too timid?

A product strategy review evaluates your plan's premise, target user, and wedge to maximize user value. It challenges whether the proposed scope is too timid or overbuilt before implementation begins, ensuring strategic clarity and focus.

What is the best way to challenge product strategy premises before engineering starts?

The best way to challenge product strategy premises is to re-evaluate whether the plan solves a real user problem and if the target user and wedge are concrete. This ensures the product direction is sharp before committing engineering resources.

How do I assess product scope and decide whether to expand or reduce it?

Assess product scope by evaluating the plan against user value and shipability. Use a mode-based recommendation framework to choose between scope expansion, selective expansion, holding scope, or scope reduction, guided by explicit decision-oriented criteria.

Can I get a structured critique of my product plan at the founder level?

Yes, a founder-level critique provides a structured review of your product plan. It delivers a concise output covering the premise, scope assessment, risks, a selected recommendation mode, and a single next step tied to maximizing user value.

When do I need a product plan review for decision-making?

You need a product plan review when deciding whether to expand, selectively add, hold, or reduce scope for strategic clarity before implementation. It is used for founder or product-lead level plans to ensure the v1 is neither too timid nor overbuilt.