plan-ceo-review

Review software development plans across architecture, security, and data flow.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill plan-ceo-review-yocxy2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/yocxy2/gstack3/tree/main/plan-ceo-review
Command: npx skills add https://github.com/yocxy2/gstack3 --skill plan-ceo-review-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the gap between a rough product plan and a production-ready, ambitious strategy by forcing a rigorous, multi-section review that challenges scope, architecture, and operational assumptions.

Core Features & Use Cases

  • Strategic Challenge: Evaluates plans through four modes: Scope Expansion, Selective Expansion, Hold Scope, and Scope Reduction.
  • Deep Review Pipeline: Conducts an 11-section audit covering architecture, error handling, security, data flow, and observability.
  • Use Case: Use this when you have a draft feature specification and need to ensure it is not just functional, but architecturally sound, secure, and aligned with a 12-month growth trajectory.

Quick Start

Invoke the plan-ceo-review skill to perform a comprehensive strategy audit on the current project plan.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
What is a founder-mode strategy review for software development plans?

A strategy review evaluates software development plans through a multi-dimensional audit, checking architectural integrity, security, and strategic ambition to ensure production readiness.

How do I review a system architecture plan for failure modes and data flows?

Review system architecture by conducting an 11-section audit covering error handling, security, data flow, and observability, systematically evaluating failure modes and long-term technical trajectory to validate project readiness.

When do I need to run a strategic challenge on a feature specification?

Run a strategic challenge when you have a draft feature specification and must verify it is architecturally sound and aligned with a 12-month growth trajectory.

Can I use this strategy review to evaluate scope reduction or selective expansion?

Yes, the strategy review evaluates plans through four modes: Scope Expansion, Selective Expansion, Hold Scope, and Scope Reduction, challenging operational assumptions and scope boundaries.

Does the strategy audit require any specific dependencies or environments?

No specific dependencies are required to run the strategy audit, but it applies to product strategy, system design, and implementation planning phases within the gstack ecosystem.

What distinguishes a rigorous strategy review from a standard feature specification check?

A rigorous strategy review forces an 11-section audit that challenges scope, architecture, and operational assumptions, moving beyond basic functionality to validate long-term technical trajectory and system observability.