plan-ceo

Guide product direction through scope expansion, hold, and reduction modes.

6|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Himanshu-Sangshetti/cursor-stack --skill plan-ceo-himanshu-sangshetti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-ceo
Source: https://github.com/Himanshu-Sangshetti/cursor-stack/tree/main/plan-ceo
Command: npx skills add https://github.com/Himanshu-Sangshetti/cursor-stack --skill plan-ceo-himanshu-sangshetti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan CEO mode challenges whether you're building the right thing, guiding founder-level decision-making with structured guardrails.

Core Features & Use Cases

  • Provides founder/CEO style critique to question scope, identify risks, and align on a high-impact plan.
  • Enables three modes—SCOPE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION—to steer product direction and prioritization.
  • Suitable for early-stage strategy, feature bets, and roadmap decisions with explicit tradeoffs and guardrails.

Quick Start

Instruct the assistant to adopt Founder/CEO mode and request a rigorous, 10-star version of the plan.

Frequently Asked Questions about plan-ceo

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

FAQPage Schema
To validate product direction, use a founder-level critique framework that challenges your scope, identifies risks, and aligns on a high-impact plan.▼

Scope reduction applies when you need to prioritize features and minimize risks by cutting non-essential elements from your product roadmap to maintain strategic focus.

When do I need to apply scope expansion versus scope reduction for feature bets?▼

Apply scope expansion to explore new feature bets and growth opportunities, whereas scope reduction applies when you must minimize risks and prioritize existing roadmap commitments.

How do I get a rigorous founder-level critique of my early-stage strategy?▼

To get a rigorous founder-level critique, instruct the assistant to adopt CEO mode and request a 10-star version of your plan to identify risks and align on high-impact tradeoffs.

What is the best way to question scope and identify risks in a roadmap decision?▼

The best way to question scope is by applying structured guardrails that evaluate explicit tradeoffs across scope expansion, hold scope, and scope reduction scenarios for roadmap decisions.

Can I use this approach for early-stage strategy and feature bets?▼

Yes, this approach is suitable for early-stage strategy and feature bets because it provides structured guardrails and explicit tradeoffs to guide founder-level decision-making.