gstack-openclaw-ceo-review

Review product and engineering plans for risks, scope, and strategic alignment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product plans often contain unaddressed edge cases, missed strategic opportunities, flawed scope, or unvalidated premises that lead to wasted engineering effort, failed launches, or subpar user outcomes. This Skill eliminates those gaps by enforcing rigorous, structured review aligned with how top CEOs and founders evaluate plans.

Core Features & Use Cases

  • 4 Flexible Review Modes: Choose between scope expansion (dream big for 10x impact), selective expansion (cherry-pick opportunities while holding baseline scope), hold scope (maximum rigor for bulletproof plans), or scope reduction (ruthless cuts to minimum viable version).
  • 11 Structured Review Sections: Covers architecture, error handling, security, data flows, code quality, testing, observability, database design, API contracts, performance, and UX to catch every potential issue.
  • CEO Cognitive Patterns: Applies proven founder-mode thinking instincts (inversion, edge case paranoia, focus as subtraction) to challenge assumptions and surface hidden risks.
  • Use Case: A product manager preparing a new feature plan can use this Skill to identify unaddressed failure modes, spot high-impact scope expansions, and ensure the plan is aligned with long-term business goals before engineering starts work.

Quick Start

Use the gstack-openclaw-ceo-review skill to review your new feature launch plan and identify unaddressed risks and scope expansion opportunities.

Frequently Asked Questions about gstack-openclaw-ceo-review

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

FAQPage Schema
How do I review a product plan to identify edge cases and strategic risks before engineering starts?

To review a product plan for edge cases and strategic risks, apply a structured CEO-grade evaluation covering architecture, error handling, security, and data flows to surface hidden flaws before implementation begins.

What is the best way to validate feature scope and optimize product plans for long-term impact?

Validating feature scope and optimizing product plans requires applying cognitive patterns like inversion and edge case paranoia to challenge assumptions, ensuring alignment with long-term business goals and maximizing impact.

Can I use scope reduction to ruthlessly cut a product plan down to a minimum viable version?

Yes, you can use scope reduction mode to ruthlessly cut a product plan down to a minimum viable version, or choose scope expansion, selective expansion, or hold scope modes depending on your strategic goals.

How does structured plan validation handle observability planning and API contract review?

Structured plan validation enforces rigorous review of observability planning and API contracts across 11 distinct sections, ensuring comprehensive error handling, database design, and performance checks are addressed.

Does this CEO review approach work for greenfield initiatives and major refactors?

Yes, this CEO review approach works for greenfield initiatives, major refactors, bug fixes, and new feature launches by applying consistent strategic alignment and risk assessment frameworks to any engineering plan.

When should I not use scope expansion mode during a product plan review?

You should avoid scope expansion mode when you need bulletproof plans for a fixed timeline; instead, use hold scope mode for maximum rigor or scope reduction mode to eliminate non-essential features.