plan-ceo-review

Review product plans on PR branches for strategic rigor and scope alignment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many product plans get reviewed without a consistent strategic lens, leading to missed opportunities, hidden risks, and scope creep. This Skill provides a CEO‑style, end‑to‑end review that enforces rigor, evaluates ambition, and applies the Completeness Principle automatically.

Core Features & Use Cases

  • Strategic Scope Analysis – challenges the premise, maps existing code leverage, and evaluates expansion, selective expansion, hold, or reduction modes.
  • Completeness & Risk Enforcement – forces full error‑handling, observability, security, and edge‑case coverage before any code changes.
  • Interactive Decision Flow – uses AskUserQuestion to let the user opt‑in to scope changes, ensuring every expansion or reduction is explicit.
  • Telemetry & Session Management – records skill usage, update checks, and telemetry preferences while respecting user privacy.
  • Use Cases – reviewing a new feature PR, evaluating a product roadmap amendment, or auditing a high‑impact design decision.

Quick Start

Invoke /plan-ceo-review on your current branch to start a comprehensive strategic review.

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 strategic rigor and scope creep?

A strategic scope analysis challenges the plan premise, maps existing code leverage, and evaluates expansion, selective expansion, hold, or reduction modes. This ensures ambition and risk are fully aligned.

What is the completeness principle in product feature planning?

The completeness principle in feature planning forces full error-handling, observability, security, and edge-case coverage. It ensures every expansion or reduction decision is explicit before any code changes are implemented.

How do I evaluate expansion or reduction decisions for a roadmap amendment?

Evaluating expansion or reduction decisions uses an interactive flow to challenge the premise and map existing code leverage. This prompts explicit user opt-in for any scope changes during the review.

Can I enforce completeness and error handling during a PR branch code review?

Yes, you can enforce completeness and error handling during a PR branch code review. A CEO-mode strategic review audits ambition, risk, and edge-case coverage directly on the branch before changes are merged.

Does a strategic plan review work for high-impact design decisions?

A strategic plan review works for high-impact design decisions by auditing scope and completeness. It challenges the premise, evaluates risk, and determines whether expansion, hold, or reduction mode is appropriate.