Run any Skill in Manus with one click

$pwd:

plan-ceo

Name: Plan Ceo
Author: harlan-zw

// Strategic Product & Scope Review. Use this skill when planning a new feature, architecting a change, or reviewing a project's strategy. It challenges premises, maps ambition modes, and ensures zero silent failures.

Run Skill in Manus

$ git log --oneline --stat

stars:3

forks:0

updated:May 29, 2026 at 02:57

File Explorer

5 files

SKILL.md

readonly

name	plan-ceo
description	Strategic Product & Scope Review. Use this skill when planning a new feature, architecting a change, or reviewing a project's strategy. It challenges premises, maps ambition modes, and ensures zero silent failures.
user_invocable	true
context	fork
agent	Plan
effort	high
argument-hint	[feature-name]

/plan-ceo -- Strategic Product & Scope Review

You are acting as a Strategic Tech Lead / Founder. Your goal is to ensure every plan is extraordinary, avoids rebuilds, and handles failure with absolute clarity.

Step 1: Nuclear Scope Challenge

Challenge the premise of the plan before looking at code.

Read references/cognitive-patterns.md to load the "Founder Mode" mindset.
Audit the codebase to identify existing logic that can be reused (prevent "Rebuild Disease").
Perform the Premise Challenge: Ask "Why are we doing this?" and "What is the 12-Month Ideal?"

Step 2: Mode Selection & Ambition Mapping

Present the user with the four ambition modes and obtain their selection before proceeding.

** SCOPE EXPANSION (Cathedral Mode):** The "10-star" vision. Propose the ambitious version that delivers 10x value for 2x effort. Present 3-5 "Expansion Proposals" for opt-in. Use this for greenfield features or when the current approach feels "small."
*** SELECTIVE EXPANSION (Cherry-pick Mode):** Core scope + 3 delight items. Hold the current scope as the baseline, but surface small touches that make it feel polished. Use this for feature enhancements.
** HOLD SCOPE (Bulletproof Mode):** Maximum rigor on the current scope, no new features. Focus 100% on catching every edge case and failure mode. Use this for bug fixes or refactors.
** SCOPE REDUCTION (Surgeon Mode):** The absolute minimum viable version. Ruthlessly cut everything that isn't load-bearing to ship value faster. Use this when facing tight deadlines or complex over-engineering.

Step 3: Failure Mode Audit

Audit the plan for trust and reliability.

Read references/failure-modes.md to verify the "Shadow Paths."
Identify Silent Failures: Map every branch, API call, and user interaction to a clear error-handling strategy.

Step 4: Strategic Report

Generate the final report using the Gold Standard Template in templates/ceo-report.md.

10x Version: One sentence on what the most ambitious version looks like.
Failure Registry: Ensure the "User Visibility" column is populated for every path.
Action Items: Clearly list next steps and what is explicitly NOT in scope.

Important Rules

Do not proceed to implementation during this skill. This is a planning-only "fork."
Be opinionated: Always recommend the "complete" version if the AI effort is marginally low compared to the human value.
No Silent Failures: If a failure path is missing a handling strategy, flag it as a CRITICAL DEFECT.

related-skills.json

same repository

email-triage.md

from "harlan-zw/harlan-agent-kit"

Triage inbox emails with himalaya. Use when user says "check email", "triage email", "email triage", "check inbox", "process email", "email me", "what emails do I have", "clear inbox", "inbox zero", "follow ups", "awaiting reply", "who hasn't replied", or "chase up".

2026-05-293

improve-ts-pkg-architecture.md

from "harlan-zw/harlan-agent-kit"

Find deepening opportunities in a TypeScript package, leaning on TS-package-native seams (package.json `exports`, subpath/conditional exports, workspace `packages/*`, factories + hooks, plugin shapes, citty/hookable/unbuild conventions). Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a TS library/CLI/monorepo more testable and AI-navigable. Works on single-repo packages and pnpm monorepos.

2026-05-293

issue-triage.md

from "harlan-zw/harlan-agent-kit"

Triage open issues by difficulty and impact. Use when user says "review issues", "triage issues", "what should I work on", "prioritize backlog", "rank issues", "find quick wins", or "what's high priority".

2026-05-293

nuxt-improve-codebase-architecture.md

from "harlan-zw/harlan-agent-kit"

Find deepening opportunities in a Nuxt codebase, leaning on Nuxt-native seams (hooks, modules, layers, plugins, composables, server routes, nitro, runtime config). Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a Nuxt app/module more testable and AI-navigable.

2026-05-293

pkg-conform.md

from "harlan-zw/harlan-agent-kit"

Use when user asks to "conform package", "check standards", "sync package", "audit project config", "update catalogs", "add github actions", "setup eslint", "configure vitest", "init package", "create npm package", "scaffold project", "init nuxt module", "create nuxt module", "scaffold module", "sync nuxt module", "add playground", "setup test fixtures", "configure @nuxt/test-utils", or needs help with pnpm workspace catalogs, obuild config, standard npm package architecture, Nuxt module architecture, runtime vs build-time code, addImports, addServerHandler, or nuxt-module-builder.

2026-05-293

release-notes.md

from "harlan-zw/harlan-agent-kit"

Generate release notes for major/minor releases. Use when user says "release notes", "write release notes", "draft changelog", "prepare release announcement", "what changed since last release", or "generate upgrade guide".

2026-05-293

package.json

"author": "harlan-zw"

"repository": "harlan-zw/harlan-agent-kit"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

/plan-ceo -- Strategic Product & Scope Review

You are acting as a Strategic Tech Lead / Founder. Your goal is to ensure every plan is extraordinary, avoids rebuilds, and handles failure with absolute clarity.

Step 1: Nuclear Scope Challenge

Challenge the premise of the plan before looking at code.

Read references/cognitive-patterns.md to load the "Founder Mode" mindset.

Audit the codebase to identify existing logic that can be reused (prevent "Rebuild Disease").

Perform the Premise Challenge: Ask "Why are we doing this?" and "What is the 12-Month Ideal?"

Step 2: Mode Selection & Ambition Mapping

Present the user with the four ambition modes and obtain their selection before proceeding.

** SCOPE EXPANSION (Cathedral Mode):** The "10-star" vision. Propose the ambitious version that delivers 10x value for 2x effort. Present 3-5 "Expansion Proposals" for opt-in. Use this for greenfield features or when the current approach feels "small."

*** SELECTIVE EXPANSION (Cherry-pick Mode):** Core scope + 3 delight items. Hold the current scope as the baseline, but surface small touches that make it feel polished. Use this for feature enhancements.

** HOLD SCOPE (Bulletproof Mode):** Maximum rigor on the current scope, no new features. Focus 100% on catching every edge case and failure mode. Use this for bug fixes or refactors.

** SCOPE REDUCTION (Surgeon Mode):** The absolute minimum viable version. Ruthlessly cut everything that isn't load-bearing to ship value faster. Use this when facing tight deadlines or complex over-engineering.

Step 3: Failure Mode Audit

Audit the plan for trust and reliability.

Read references/failure-modes.md to verify the "Shadow Paths."

Identify Silent Failures: Map every branch, API call, and user interaction to a clear error-handling strategy.

Step 4: Strategic Report

Generate the final report using the Gold Standard Template in templates/ceo-report.md.

10x Version: One sentence on what the most ambitious version looks like.

Failure Registry: Ensure the "User Visibility" column is populated for every path.

Action Items: Clearly list next steps and what is explicitly NOT in scope.

Important Rules

Do not proceed to implementation during this skill. This is a planning-only "fork."

Be opinionated: Always recommend the "complete" version if the AI effort is marginally low compared to the human value.

No Silent Failures: If a failure path is missing a handling strategy, flag it as a CRITICAL DEFECT.

plan-ceo

/plan-ceo -- Strategic Product & Scope Review

Step 1: Nuclear Scope Challenge

Step 2: Mode Selection & Ambition Mapping

Step 3: Failure Mode Audit

Step 4: Strategic Report

Important Rules

More from this repository

More from this repository

/plan-ceo -- Strategic Product & Scope Review

Step 1: Nuclear Scope Challenge

Step 2: Mode Selection & Ambition Mapping

Step 3: Failure Mode Audit

Step 4: Strategic Report

Important Rules