gstack-openclaw-ceo-review

Review technical plans for risks, scope, and quality.

Updated Jun 4, 2026

Search Tags:#quality assurance #technical review #plan optimization #risk identification #CEO review

Ready to run

npx skills add https://github.com/burgebj/gstack --skill gstack-openclaw-ceo-review-burgebj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-openclaw-ceo-review
Source: https://github.com/burgebj/gstack/tree/main/openclaw/skills/gstack-openclaw-ceo-review
Command: npx skills add https://github.com/burgebj/gstack --skill gstack-openclaw-ceo-review-burgebj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps in conducting a comprehensive CEO-level review of plans, ensuring the highest quality and best user outcomes.

Core Features & Use Cases

CEO Plan Review: Analyze and challenge proposals, expand scope, or reduce to minimal viable product.
Philosophy and Directives: Follow a set of prime directives like zero silent failures, named errors, data flow tracing, and observability.
Cognitive Patterns: Utilize 15 cognitive patterns to shape perspective throughout the review.
Review Sections: Cover architecture, error & rescue mapping, security, data flow, code quality, testing, observability, database, API design, performance, and design.

Quick Start

Run a CEO review on your plan by executing the gstack-openclaw-ceo-review skill and follow the structured approach.

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 conduct a technical review of a system architecture plan?▼

A CEO review evaluates technical plans by assessing system architecture, error handling, security, data flow, and code quality to optimize scope and identify risks. It follows a structured review process requiring an input plan document.

What is included in a CEO-level plan review for technical projects?▼

A CEO-level plan review covers architecture, error and rescue mapping, security, data flow, code quality, testing, observability, database, API design, performance, and design. It applies 15 cognitive patterns to challenge proposals and optimize scope.

How do I identify risks and optimize scope in a software development plan?▼

You identify risks and optimize scope by challenging proposals against prime directives like zero silent failures, named errors, data flow tracing, and observability. This process helps expand or reduce the plan to a minimal viable product.

Can I use a structured review process to assess error handling and security in my plan?▼

Yes, you can assess error handling and security by executing a structured review process on your input plan document. This maps errors, evaluates rescue paths, and audits security protocols to ensure zero silent failures.

What are the limitations of using cognitive patterns for plan optimization?▼

The metadata does not specify explicit limitations, but the approach relies on 15 predefined cognitive patterns and requires a complete input plan document to effectively evaluate architecture, data flow, and API design.