plan-ceo-review

Evaluate project plans for scope, risks, dependencies, and milestones.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables rigorous CEO-style evaluations of product and project plans, surfacing scope gaps, risks, and opportunities early to improve outcomes.

Core Features & Use Cases

  • Modeled plan critique: supports modes like SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION to shape the plan.
  • Structured decision logs: outputs a backlog of changes and a decision log to guide stakeholders.
  • AskUserQuestion guided interactions: uses prompts to surface expansions or reductions with explicit tradeoffs.

Quick Start

Ask me to start a CEO-grade plan review for this project.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I conduct a CEO-level plan review for product strategy and engineering timelines?

A CEO-level plan review evaluates project plans by analyzing scope, risks, dependencies, and milestones to surface high-impact improvements. It applies rigorous critique to product strategy and engineering timelines, explicitly escalating unsound choices to ensure robust risk mitigation.

What is the best way to identify scope gaps and mitigate risks in a project plan?

Identifying scope gaps and mitigating risks requires modeling plan critique through modes like scope expansion, selective expansion, hold scope, and scope reduction. This structured evaluation surfaces edge-case handling gaps and ensures complete observability across project milestones.

How do I generate a decision log and backlog of changes from a project plan critique?

Generating a decision log and backlog of changes requires applying structured plan critique to end-to-end project reviews. The process outputs a plan backlog of necessary modifications alongside a decision log to guide stakeholders through clear decision gates.

Can I use guided prompts to evaluate tradeoffs between scope expansion and scope reduction?

Yes, you can use guided prompts to evaluate tradeoffs between scope expansion and scope reduction. The AskUserQuestion interactions surface explicit tradeoffs for stakeholders, ensuring high-impact improvements align with product strategy and engineering timelines.

When do I need to escalate unsound choices during a project plan review?

You need to escalate unsound choices during a project plan review when the evaluation of scope, risks, dependencies, and milestones reveals incomplete scope coverage or inadequate edge-case handling. Explicit escalation ensures decision gates are met and risk mitigation is sound.