gstack-openclaw-ceo-review

Reviews engineering plans across eleven sections with scope-mode selection and issue-by-issue challenge.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often ship with hidden failure modes, unexamined scope, and missing observability. This Skill applies a rigorous CEO-style review that challenges the premise, maps every error path, and forces explicit scope decisions before any code is written. ## 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 services, run this review to surface unnamed error paths, missing tests, and N+1 query risks, then decide which expansion ideas to adopt one at a time. ## 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 engineering plan before implementation?

Run a CEO plan review that first challenges the premise and scope, then evaluates eleven sections covering architecture, errors, security, data flows, tests, observability, database, API, performance, and UX. Each issue is raised one at a time for explicit decisions.

What is scope expansion vs scope reduction in plan review?

Scope expansion proposes ambitious improvements the user opts into individually, while scope reduction cuts the plan to the minimum viable version. The review also supports selective expansion and hold-scope modes depending on context.

Does this review skill make code changes?

No, the skill explicitly forbids code changes and implementation. Its only job is to review the plan, surface issues, and produce a summary with completion status of DONE, DONE_WITH_CONCERNS, or BLOCKED.

When should I use hold scope mode instead of expansion?

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

What does the CEO review summary include?

The summary lists the selected mode, the top three strongest challenges, the recommended path forward, accepted scope, deferred items with reasons, and explicitly excluded items. It is saved to a memory directory for future reference.