plan-ceo-review

Reviews product plans through CEO-mode scope expansion, reduction, and rigor analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product plans often suffer from unchallenged assumptions, timid scope, or bloated scope. This Skill stress-tests a plan the way a founder would: rethinking the problem, challenging premises, and deciding whether to expand, hold, or cut scope before engineering time is committed. ## Core Features & Use Cases - Four Review Modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope plus cherry-picked expansions), HOLD SCOPE (maximum rigor), and SCOPE REDUCTION (strip to essentials). - Interactive Decision Briefs: Uses structured AskUserQuestion decision briefs with recommendations, tradeoffs, and completeness scores so every scope call is explicit. - Context-Aware: Loads prior CEO plans, recent design docs, and past review activity for the project so reviews build on history instead of starting cold. - Use Case: You have a draft plan for a new feature and suspect it is thinking too small. Invoke the review to get a 10-star product vision, a challenge to your premises, and a concrete recommendation on what to expand or cut. ## Quick Start Ask the assistant to run a CEO-mode review on your current plan with a prompt like "rethink this plan and tell me if it is ambitious enough".

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 for scope and ambition?

Invoke the plan-ceo-review skill with a request like "think bigger" or "strategy review". It walks through four modes, from scope expansion to scope reduction, and presents each decision as a structured brief with a recommendation and tradeoffs.

What review modes does plan-ceo-review support?

It supports four modes: SCOPE EXPANSION for dreaming big, SELECTIVE EXPANSION for holding scope while cherry-picking additions, HOLD SCOPE for maximum rigor, and SCOPE REDUCTION for stripping a plan to essentials.

When should I use a CEO-style plan review instead of an engineering review?

Use it when the open questions are about product direction, ambition, and premises rather than architecture or implementation. It rethinks the problem itself; engineering review skills handle technical soundness afterward.

Does plan-ceo-review work non-interactively or in automated sessions?

It is interactive by design and depends on an AskUserQuestion tool variant. In spawned or orchestrated sessions it auto-chooses recommended options, and if no question tool is available it stops and reports itself as blocked.

What context does the skill use when reviewing a plan?

It loads prior CEO plans, recent design documents, and recent review activity for the current project from the gstack project directory, so recommendations account for earlier decisions rather than starting from scratch.