plan-ceo-review

Evaluate feature proposal plans with Expansion, Hold, and Reduction modes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan reviews for CEO-mode product proposals, enabling rigorous, transformative evaluation of scope, risk, and opportunity before commit.

Core Features & Use Cases

  • Comprehensive mode-driven review (Expansion, Hold, Reduction) to shape product scope and technical plan.
  • Architecture and risk articulation with ASCII diagrams, failure modes, and rescue paths.
  • Deliverables: a structured plan with decisions, next steps, and guardrails.

Quick Start

Provide a feature brief and run a CEO-mode plan review to generate a prioritized, auditable plan.

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 feature plan from a CEO or founder perspective?▼

Conduct a CEO-mode plan review to evaluate feature briefs from a founder perspective, ensuring clear scope, ownership, and success criteria before committing resources.

What is the best way to evaluate risk and failure modes in a feature proposal?▼

Map failure modes and rescue paths using ASCII architecture diagrams to produce a structured plan with implementation guardrails and auditable risk mappings.

How do I structure a roadmap pitch to ensure clear scope and ownership?▼

Run a strategic plan review on early-stage briefs and roadmap pitches to enforce clear scope and ownership, yielding an auditable plan with decisions and defined next steps.

Can I use ASCII architecture diagrams for QA planning and feature planning?▼

Use ASCII architecture diagrams during feature planning to articulate technical design and risk, generating QA plans with implementation guardrails and failure mode mappings.

When should I use Expansion, Hold, or Reduction modes for plan reviews?▼

Apply Expansion, Hold, or Reduction modes during plan reviews to shape product scope and technical plans, managing risk and opportunity before implementation commit.