ceo-review

Reframe feature requests into three scope options with rationale.

11|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/KSD-CO/IronCode --skill ceo-review-ksd-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ceo-review
Source: https://github.com/KSD-CO/IronCode/tree/main/.ironcode/skill/ceo-review
Command: npx skills add https://github.com/KSD-CO/IronCode --skill ceo-review-ksd-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps founders and product thinkers avoid literal feature requests by diagnosing the real job to be done and proposing a 10-star version.

Core Features & Use Cases

  • Reframe requests to identify the real user goal and outcome.
  • Present exactly three scope options (A) SCOPE EXPANSION, (B) HOLD SCOPE, (C) SCOPE REDUCTION) with clear tradeoffs and rationale.
  • Enable an interactive decision step via a question tool to select the preferred path and plan subsequent steps.

Quick Start

Ask your assistant to reframe a feature request into the real job and present three scope options.

Frequently Asked Questions about ceo-review

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

FAQPage Schema
How do I reframe a feature request to identify the real user job?

To reframe a feature request, analyze the input to diagnose the real job to be done and propose a 10-star solution instead of taking the request literally. This uncovers the actual user goal and desired outcome.

What are scope options in product strategy decision-making?

Scope options in product strategy are three distinct paths: scope expansion, hold scope, and scope reduction. Each path presents clear tradeoffs and rationale to help founders choose the optimal direction for a feature request.

When do I need to reframe a product request instead of building it literally?

You need to reframe a product request when founders want to avoid literal feature builds. Reframing diagnoses the real job to be done to propose a 10-star version that achieves the actual user outcome.

How do I evaluate scope tradeoffs for a new feature request?

You evaluate scope tradeoffs by reviewing clear rationale for scope expansion, hold scope, and scope reduction. An interactive decision step then prompts you to select a preferred path and plan subsequent steps based on that choice.

Can I use an interactive question tool to choose a product strategy path?

Yes, you can use an interactive question tool to choose a product strategy path. The tool prompts you to select among scope expansion, hold scope, or scope reduction, and outlines next steps based on your selected option.

What is the best way to avoid literal feature requests in founder mode?

The best way to avoid literal feature requests in founder mode is to diagnose the real job to be done and reframe the problem. This approach proposes a 10-star solution rather than executing the initial request literally.