plan-ceo-review

Plans architecture reviews using EXPAND, HOLD, and REDUCE modes to align technical work with business goals.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill plan-ceo-review-xza85hrf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/Xza85hrf/claude-code-agent-kit/tree/main/.claude/skills/architecture/plan-ceo-review
Command: npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill plan-ceo-review-xza85hrf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans architecture reviews from a founder's perspective to challenge assumptions and align technical work with business goals before implementation.

Core Features & Use Cases

  • Provides mode-based planning (EXPAND, HOLD, REDUCE) to shape problem framing, scope, and prioritization.
  • Guides structured decision-making, risk assessment, and stakeholder alignment across teams.
  • Produces actionable planning artifacts and asks focused questions to unlock high-quality outcomes.

Quick Start

Provide a CEO review planning brief for an architecture initiative using the EXPAND/HOLD/REDUCE modes.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I plan an architecture review to align technical work with business goals?

Architecture review planning from a founder's perspective challenges assumptions and aligns technical initiatives with business goals. It uses structured decision-making, risk assessment, and stakeholder alignment to produce actionable planning artifacts before implementation begins.

What is the EXPAND, HOLD, and REDUCE framework for scope decisions?

The EXPAND, HOLD, and REDUCE modes are a planning framework used to guide problem framing, scope decisions, and prioritization. EXPAND explores new possibilities, HOLD maintains current scope, and REDUCE narrows focus to align technical work across stakeholders and timelines.

When do I need a founder's perspective for architecture governance and risk management?

You need a founder's perspective for architecture governance when technical decisions require strategic alignment with business goals. It helps challenge assumptions, frame problems correctly, assess risks, and ensure stakeholder alignment before committing to implementation timelines.

How do I structure stakeholder alignment and decision-making for a technical strategy review?

Structure stakeholder alignment by applying mode-based planning to shape prioritization and scope. Use structured questions and risk assessment to guide decision-making across teams, producing actionable planning artifacts that unlock high-quality outcomes.

Can I use this approach to challenge technical assumptions before starting implementation?

Yes, this approach specifically challenges assumptions before implementation begins. By applying EXPAND, HOLD, and REDUCE modes to problem framing and scope decisions, it ensures technical initiatives are validated against business goals and stakeholder requirements.

What are the limitations of using mode-based planning for architecture reviews?

Mode-based planning for architecture reviews requires a clear CEO review planning brief to function effectively. Without accurate stakeholder input and defined business goals, the EXPAND, HOLD, and REDUCE framework cannot produce comprehensive planning artifacts or meaningful risk assessments.