plan-ceo-review

Review product plans using a four-mode CEO/founder framework.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/onlypfachi/chief --skill plan-ceo-review-onlypfachi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/onlypfachi/chief/tree/main/plan-ceo-review
Command: npx skills add https://github.com/onlypfachi/chief --skill plan-ceo-review-onlypfachi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The CEO/founder-mode plan review helps teams rethink problems, identify higher-value scope opportunities, and decide between expansion or constraint with explicit tradeoffs and auditable rationales.

Core Features & Use Cases

  • Structured four-mode review (Expansion, Selective Expansion, Hold Scope, Scope Reduction) to balance ambition with practicality.
  • Proactive risk assessment, edge-case consideration, and traceable decision documentation for stakeholders.
  • Built-in support for design-checks, TODOS mapping, and architecture considerations to improve plan quality and alignment.

Quick Start

Describe the plan to review and I will guide you through expanding or narrowing scope using the four modes.

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 from a CEO perspective to maximize strategic impact?

A CEO product plan review balances ambition and practicality using a structured four-mode framework: Expansion, Selective Expansion, Hold Scope, and Scope Reduction. These modes help teams rethink problems and decide between scope expansion or constraint with explicit tradeoffs.

When should I use scope reduction instead of selective expansion during a strategy review?

Apply scope reduction when disciplined constraint is required, and selective expansion when targeting specific high-value opportunities. The framework enforces explicit tradeoffs and auditable rationales, ensuring stakeholders understand exactly why a specific mode was chosen for the product plan.

How do I document tradeoffs and risk assessments when expanding or narrowing project scope?

Document tradeoffs and risk assessments by enforcing proactive risk evaluation, edge-case consideration, and traceable decision documentation. This provides an auditable rationale for stakeholders, ensuring that scope expansion or reduction decisions are fully transparent and defensible.

Can I map TODOS and architecture considerations during a design review?

Yes, you can map TODOS and architecture considerations during a design review. The review process includes built-in support for comprehensive design checks and architecture considerations to improve overall plan quality and strategic alignment.

What is the best way to guide a team through expanding or narrowing a product plan's scope?

The best way to guide a team through scope adjustments is by describing the plan for review and applying a structured four-mode framework. This method evaluates proactive risks and edge cases to produce a robust plan with traceable decision documentation.