plan-ceo-review

Reviews implementation plans with CEO-mode scope analysis and failure-mode mapping.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill plan-ceo-review-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/gstack-plan-ceo-review
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill plan-ceo-review-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often ship with unchallenged premises, hidden failure modes, and scope that is either too timid or too bloated. This Skill performs a founder-mode strategic review of a plan before any code is written, catching landmines early. ## Core Features & Use Cases - Four Review Modes: Scope Expansion (dream big), Selective Expansion (cherry-pick expansions), Hold Scope (maximum rigor), and Scope Reduction (strip to essentials), each chosen explicitly by the user. - Pre-Review System Audit: Inspects git history, diffs, TODOs, design docs, and handoff notes to ground the review in the actual repository state. - Rigorous Plan Analysis: Maps error/rescue paths, data-flow shadow paths, edge cases, observability gaps, and produces mandatory ASCII diagrams for non-trivial flows. - Use Case: Before implementing a new feature branch, run this Skill to challenge the plan's premises, decide whether scope should grow or shrink, and surface every failure mode with named exceptions and test coverage expectations. ## Quick Start Ask the AI to run a CEO-mode review of the current branch's plan and challenge whether the scope 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 before implementation?

Run this Skill on the branch containing your plan. It audits the repository state, challenges the plan's premises, and walks through scope, failure modes, error paths, and test coverage using one of four review modes you select.

What are the four review modes in plan-ceo-review?

Scope Expansion pushes ambition upward, Selective Expansion holds scope while offering cherry-pickable additions, Hold Scope applies maximum rigor to the existing plan, and Scope Reduction strips the plan to its minimum viable core.

Does plan-ceo-review make code changes?

No. The Skill explicitly forbids code changes and implementation. Its only job is to review the plan with rigor and present scope decisions as explicit user opt-ins via questions.

Can I use plan-ceo-review without a design doc?

Yes, but it will offer to run the office-hours skill first to produce a structured problem statement. You can skip that offer and proceed with a standard review using only the repository audit.

When should I not use a CEO-style plan review?

Avoid it for trivial changes, quick bug fixes, or when the problem itself is still undefined. If you cannot articulate the problem, the Skill redirects you to office-hours for problem framing first.