plan-ceo-review
From the author
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, and expand or cut scope when that makes a better product — in one of four modes: scope expansion, selective expansion, hold scope, scope reduction. Then review the plan section by section: architecture, error and rescue map, security, data flow and edge cases, code quality, tests, performance, observability, rollout, trajectory and UX. Use when asked to "think bigger", "expand scope", "strategy review", "rethink this" or "is this ambitious enough", or when a plan could be thinking bigger.
Install
npx skills add Bevel-Software/Hexis --skill plan-ceo-review -a claude-code
Installs to .claude/skills/plan-ceo-review/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- plan-eng-reviewBevel-Software/HexisEng-manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance — walking through issues one at a time with opinionated recommendations. Use when asked to "review the architecture", "engineering review", "tech review" or "lock in the plan", and when someone has a plan or design doc and is about to start coding.Planning★ 120
- review-plantobihagemann/turboReview a plan by running internal reviews and a peer review in parallel and returning combined findings. Use when the user asks to "review my plan", "check my plan", "critique my plan", or wants feedback on a plan.Planning★ 416
- plan-reviewmvschwarz/openrigMulti-perspective review of a feature plan or requirements doc before development begins. Evaluates from strategy, design/UX, and engineering angles to catch gaps early.Planning★ 8.2K
- plan-modeCodeAlive-AI/ai-driven-developmentUse this skill when the user asks to plan, design, scope, estimate, or implement a feature, bug fix, refactor, migration, integration, API change, UI change, or other project modification. Enforces a planning gate before editing code — investigate project context, analyze the task, surface ambiguities, contradictions, risks, dependencies, and blockers, ask focused questions, produce an evidence-based step-by-step plan, and implement only after explicit user approval. Not for trivial one-line edits, pure questions about the codebase, or changes the user has already reviewed and approved for direct implementation.Planning★ 166
- review-spectranhieutt/software_development_departmentReviews a product, technical, API, UI, or implementation spec for completeness, testability, architectural fit, and readiness before planning or implementation.Planning★ 74
- create-test-plantobihagemann/turboAnalyze what changed and generate a structured test plan at .turbo/test-plans/<slug>.md covering four escalating levels: basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Use when the user asks to "create a test plan", "plan tests", "what should I test", "generate test scenarios", "test plan for this PR", or "what are the test cases".Testing★ 416
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in