plan-ceo-review
by garrytanplan-ceo-review is a CEO/founder-style review skill for strategic planning. It helps agents rethink plans, test assumptions, and choose whether to expand, hold, or reduce scope. Use it when you need decision quality on whether a plan is ambitious enough, not just a quick edit or tactical checklist.
This skill scores 68/100, which means it is list-worthy but limited: directory users get a clear CEO-style review workflow and triggers, yet should expect to rely on the large body text for execution details because the front matter and support files are sparse. It is useful for agents that need a structured "think bigger / challenge premises" planning pass, but it is not a highly polished install decision page.
- Clear triggerability: explicit triggers like "think bigger," "expand scope," "strategy review," and "rethink this plan".
- Strong operational framing: four named modes—SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION—give agents a concrete way to choose behavior.
- Substantial workflow content: very large SKILL.md body with many headings and workflow/constraint signals suggests more than a stub.
- Sparse repository scaffolding: no scripts, references, resources, rules, assets, readme, or metadata files to support adoption or trust.
- Front-matter description is short and the directory evidence shows placeholder markers, so users may need to inspect the full body to understand edge cases and exact execution.
Overview of plan-ceo-review skill
What plan-ceo-review does
plan-ceo-review is a CEO/founder-style review skill for strategic planning. It is meant for moments when a plan needs to be rethought, not just edited: “think bigger,” “expand scope,” “strategy review,” or “is this ambitious enough?” The plan-ceo-review skill helps an agent challenge premises, weigh scope changes, and decide whether to expand, hold, or reduce scope.
Who it fits best
This skill is best for product leads, founders, PMs, and agents working on roadmap, positioning, or high-stakes plan review. If you need a fast execution checklist, this is not the right fit. If you need judgment about whether the plan itself is aiming at the right outcome, plan-ceo-review for Strategic Planning is a better match.
Core differentiator
The main value is decision quality under ambiguity. The skill is built around four modes: scope expansion, selective expansion, hold scope, and scope reduction. That gives the reviewer a structured way to either raise ambition or tighten discipline instead of defaulting to vague “sounds good” feedback.
How to Use plan-ceo-review skill
Install and activate
Use the plan-ceo-review install flow from your skills manager, then invoke it when the request includes strategic uncertainty or a prompt to rethink scope. In the repo, start with SKILL.md, then inspect SKILL.md.tmpl to understand how the skill is assembled. There is no dedicated install script in this repo, so the markdown itself is the source of truth.
Give it a plan, not a vibe
The plan-ceo-review usage pattern works best when you provide a concrete artifact: a draft plan, roadmap, PRD, launch brief, or decision memo. A weak prompt is “review this idea.” A stronger prompt is: “Review this Q3 product plan for scope, ambition, and missing bets. Tell me whether to expand, hold, or cut scope, and why.” Include constraints, success metrics, and what tradeoffs are already known.
Read the right files first
For practical plan-ceo-review guide use, read SKILL.md first, then look for the embedded context queries in the frontmatter. Those queries pull prior CEO plans, recent design docs, and recent review activity from the local gstack project store. That matters because this skill is designed to compare your current plan against prior strategic context, not just assess the text in isolation.
Workflow that produces better output
A good flow is: draft the plan, ask the skill for a CEO review, then revise the plan based on the mode it recommends. If the output is too broad, narrow the ask to one decision: “Should we expand scope for this launch?” If the output is too narrow, ask it to identify the 10-star version before comparing against current scope. That keeps the review anchored to an actual decision, which is where the skill is strongest.
plan-ceo-review skill FAQ
Is this the same as a normal prompt?
No. A normal prompt can ask for strategy feedback, but the plan-ceo-review skill adds a reusable review structure, trigger language, and project-aware context. That reduces guesswork when you need a repeatable review for Strategic Planning rather than one-off brainstorming.
When should I not use it?
Do not use plan-ceo-review when you only need copyediting, implementation advice, or a linear task breakdown. If the question is “how do we build this?” a tactical planning skill is better. If the question is “should we make this bigger, smaller, or different?” plan-ceo-review is the right tool.
Is it beginner-friendly?
Yes, if you can describe the plan clearly. The biggest beginner mistake is asking for ambition review without sharing the actual plan or constraints. Give the objective, audience, current scope, and what “success” means, and the skill can do useful work even without deep product context.
How to Improve plan-ceo-review skill
Provide sharper decision context
The fastest way to improve plan-ceo-review results is to state the decision you want made. For example: “We have room for one more quarter of work; should we expand scope or keep this launch tight?” That is better than “make this better,” because the skill can then judge tradeoffs instead of inventing them.
Include the constraint that matters most
Strong inputs name the real limiter: engineering capacity, launch timing, user risk, brand risk, or dependency uncertainty. The skill can only recommend expansion or reduction intelligently if it knows what cannot move. This is especially important in plan-ceo-review for Strategic Planning, where ambition has to be weighed against execution reality.
Iterate on the first review
If the first output is too generic, ask for one of the four modes explicitly: “re-run in scope expansion mode,” “hold scope and find the highest-leverage cuts,” or “selective expansion only.” The skill is designed to support those pivots, so iteration should tighten the decision frame rather than reopen the whole problem.
Watch for common failure modes
The most common failure is over-scoping without a clear prize. Another is accepting a polished but shallow plan because it feels complete. Use plan-ceo-review to surface missing bets, hidden assumptions, and whether the proposal deserves to be bigger at all.