gstack-openclaw-ceo-review

Identify and challenge plan weaknesses and risk pathways in structured reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product leaders perform a thorough, risk-aware plan review by structuring scope, identifying edge cases, and ensuring explicit opt-in decisions before proceeding.

Core Features & Use Cases

  • Structured review templates covering architecture, risk, and decision points to surface gaps early.
  • Mode-driven analysis (scope expansion, selective expansion, hold scope, scope reduction) to guide decisions.
  • Final CEO-ready summary that records rationale, trade-offs, and next actions.

Quick Start

Describe your plan and mode preference, and the Skill will perform a structured CEO-review and return a summary.

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 perform a rigorous CEO-style review of an early-stage project plan?

A CEO-style plan review identifies and challenges plan weaknesses and risk pathways. It structures scope, surfaces edge cases, and enforces explicit opt-in decisions before proceeding with early-stage projects or feature scope decisions.

What is the best way to assess risk pathways and decision points in a governance review?

Assessing risk pathways in a governance review requires structured templates covering architecture, risk, and decision points. This approach surfaces gaps early and ensures risk-aware decision-making across teams before finalizing the plan.

How do I select the right scope mode for feature scope decisions?

Selecting a scope mode for feature decisions involves choosing between scope expansion, selective expansion, hold scope, or scope reduction. Mode-driven analysis guides these decisions by evaluating trade-offs and identifying potential risk pathways.

Can I use a structured review template to challenge plan weaknesses across teams?

Structured review templates can challenge plan weaknesses across teams by enforcing front-matter metadata and sectioned reviews. They identify edge cases and ensure explicit opt-in decisions are recorded during governance reviews.

What should a final CEO-ready summary include after a plan review?

A final CEO-ready summary should record the rationale, trade-offs, and next actions resulting from the plan review. It consolidates the mode-based analysis and structured critique into actionable outcomes for product leaders.