gstack-openclaw-ceo-review

Reviews plans across eleven structured sections with scope challenge and mode selection.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill gstack-openclaw-ceo-review-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-ceo-review
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/openclaw/skills/gstack-openclaw-ceo-review
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill gstack-openclaw-ceo-review-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often ship with hidden failure modes, unexamined scope, and missing error handling. This Skill performs a rigorous CEO-style plan review that challenges the premise, maps every error path, and forces explicit scope decisions before any implementation begins. ## Core Features & Use Cases - Scope Mode Selection: Choose between scope expansion, selective expansion, hold scope, or scope reduction, with context-dependent defaults based on plan type. - Eleven-Section Review: Systematically evaluates architecture, error handling, security, data flows, code quality, tests, observability, database design, API contracts, performance, and UX. - Implementation Alternatives: Produces 2-3 distinct approaches with effort and risk estimates before recommending one, requiring explicit user approval. - Use Case: Before starting a multi-file feature, run a CEO review to catch missing error handling, unmapped edge cases, and scope creep, then receive a summary of accepted scope and deferred items. ## Quick Start Ask the assistant 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 CEO plan review that challenges the premise, maps existing code leverage, and evaluates eleven sections including architecture, error handling, and tests. Each issue is raised one at a time, and no code changes are made during the review.

What is a scope expansion vs scope reduction plan review?

Scope expansion proposes ambitious improvements the user opts into individually, while scope reduction cuts the plan to the minimum viable version. Selective expansion holds the baseline and offers cherry-picked additions, and hold scope makes the current plan bulletproof.

Does a plan review skill make code changes?

No. This review skill explicitly forbids code changes and implementation. Its only job is to evaluate the plan, surface issues one at a time, and produce a summary of accepted scope and deferred items.

When should I use hold scope mode in a plan review?

Hold scope is the default for bug fixes, hotfixes, and refactors where the plan's scope is already accepted. The reviewer focuses on failure modes, edge cases, and observability without silently adding or removing scope.

What are the limitations of an AI plan review?

The review depends on the quality of the plan and context provided; it cannot verify runtime behavior or execute tests. Plans touching more than fifteen files may be recommended for scope reduction rather than full review.