gstack-openclaw-ceo-review

Reviews implementation plans across eleven sections to challenge scope, errors, and edge cases.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill gstack-openclaw-ceo-review-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-ceo-review
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/gstack/openclaw/skills/gstack-openclaw-ceo-review
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill gstack-openclaw-ceo-review-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often ship with hidden failure modes, vague error handling, and unexamined scope decisions. This Skill applies a rigorous CEO-style review to any plan before implementation, catching landmines early and forcing explicit scope decisions. ## Core Features & Use Cases - Mode-Based Scope Review: Choose between scope expansion, selective expansion, hold scope, or scope reduction, with every scope change requiring explicit user opt-in. - Eleven-Section Audit: Systematically evaluates architecture, error handling, security, data flows, code quality, tests, observability, database design, API contracts, performance, and UX. - Structured Summary Output: Produces a CEO review summary with strongest challenges, recommended path, accepted scope, and deferred items saved to memory. - Use Case: Before implementing a new feature touching multiple files, run this review to map every error path, diagram data flows, and decide whether the plan should be expanded, held, or cut to a minimum viable version. ## Quick Start Ask the AI to run a CEO review on your implementation plan and challenge its scope before writing any code.

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 an implementation plan before coding?

Run a structured plan review that evaluates architecture, error handling, security, data flows, tests, and observability section by section. This Skill walks through eleven review areas and discusses each issue with you one at a time.

What is a CEO-style plan review?

A CEO-style review challenges the premise of a plan, maps implementation alternatives, and forces explicit scope decisions. It classifies decisions by reversibility and magnitude, then either expands, holds, or reduces scope based on context.

When should I use scope reduction versus scope expansion?

Use scope reduction for plans touching many files or when a minimum viable version achieves the core outcome. Use expansion for greenfield features where a 10x better result justifies roughly 2x the effort.

Does this review skill make code changes?

No, it only reviews plans and never implements them. Its output is a structured summary covering the strongest challenges, recommended path, accepted scope, and explicitly deferred items.

What are the limitations of a plan review without implementation?

A plan review cannot catch runtime issues that only surface during execution, such as actual performance bottlenecks or integration failures. It works best paired with testing and monitoring after implementation begins.