gstack-openclaw-ceo-review

Review CEO-level product plans for risks, dependencies, and scope trade-offs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, disciplined framework for reviewing CEO-level product plans. It surfaces gaps, risks, misalignments, and growth opportunities, ensuring plans are robust, scalable, and aligned with strategic goals.

Core Features & Use Cases

  • Structured mode-driven review to enforce explicit scope decisions (Scope Expansion, Selective Expansion, Hold Scope, Scope Reduction) and ensure deliberate trade-offs.
  • Comprehensive risk, dependency, and observability mapping to surface critical failure points before execution.
  • Diagrammatic and narrative outputs that guide leadership discussions and decision-making.

Quick Start

Describe a CEO-level plan and request a 10x improvement assessment.

Frequently Asked Questions about gstack-openclaw-ceo-review

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

FAQPage Schema
What is a CEO-level product plan review and why do I need it?

A CEO-level product plan review evaluates scope decisions, timelines, and investment trade-offs to identify flaws and opportunities. You need it to surface gaps, risks, and dependency misalignments, ensuring your strategic plan is robust and scalable before execution.

How do I analyze product strategy risks and dependencies before execution?

Analyze product strategy risks by mapping critical failure points and dependencies to surface observability gaps. This structured review enforces explicit scope decisions and deliberate trade-offs, maximizing product impact by identifying misalignments before execution.

Can I use this for scope management decisions like selective expansion or scope reduction?

Yes, you can use this for scope management decisions like selective expansion or scope reduction. The review enforces explicit mode selection to ensure deliberate trade-offs are made across scope expansion, holding scope, or reduction scenarios.

What's the best way to review architecture diagrams and edge cases for product scope decisions?

The best way to review architecture diagrams and edge cases is through a mode-driven assessment that maps risks and dependencies comprehensively. This approach generates diagrammatic and narrative outputs to guide leadership discussions and validate investment trade-offs.

Does this product plan review work for assessing investment trade-offs and timeline risks?

Yes, this product plan review works for assessing investment trade-offs and timeline risks. It analyzes CEO-level plans to surface critical failure points, ensuring requirements like mandatory mode choice and thorough edge-case consideration are satisfied for stronger outcomes.

Why does my product strategy review miss growth opportunities and misalign dependencies?

Your product strategy review misses growth opportunities because it lacks comprehensive dependency mapping and explicit scope mode selection. A structured framework surfaces these misalignments by enforcing deliberate trade-offs and thorough edge-case consideration across your plan.