plan-ceo-review

Review gstack plans with founder-mode critique and risk mapping.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/abustamam/portfolio-blog --skill plan-ceo-review-abustamam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/abustamam/portfolio-blog/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/abustamam/portfolio-blog --skill plan-ceo-review-abustamam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a rigorous founder-mode plan review to help product teams critique and improve gstack strategies, ensuring clarity, risk awareness, and actionable next steps.

Core Features & Use Cases

  • Structured, founder-mode critique of strategy plans.
  • ASCII diagrams and risk/rescue mapping to surface failure modes.
  • Guidance for expansion, hold, or reduction decisions with concrete recommendations.

Quick Start

Provide your project context and request a CEO-grade review of the current plan.

Frequently Asked Questions about plan-ceo-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a founder-mode strategy review for my gstack project?

Founder-mode strategy review for gstack projects is performed by supplying project context to receive a rigorous critique, enforcing frontmatter metadata, ASCII diagrams, and risk assessments to ensure actionable next steps.

What is the best way to assess risks and map failure modes in gstack architecture plans?

Risk assessment and failure mode mapping in gstack architecture plans is achieved through structured critique that generates ASCII diagrams and rescue maps, explicitly surfacing risks to guide expansion, hold, or reduction decisions.

Can I use this approach for feature prioritization and scope decisions in complex plans?

Feature prioritization and scope decisions for complex plans are supported through mode-based decision prompts that evaluate expansion, hold, or reduction workflows, ensuring concrete recommendations tailored to your project context.

Does the plan review process require specific metadata formats like frontmatter?

The plan review process requires frontmatter-based metadata to structure the review session, alongside ASCII diagrams and rescue maps, ensuring comprehensive strategy sessions maintain clarity and risk awareness.

When do I need mode-based decision prompts for scope reduction workflows?

Mode-based decision prompts for scope reduction workflows are needed when complex gstack plans require rigorous evaluation, guiding whether to expand, hold, or reduce features based on risk assessments and strategic clarity.