ceo-advisor
$
npx mdskill add alirezarezvani/claude-skills/ceo-advisorStrategic leadership frameworks for vision, fundraising, board management, culture, and stakeholder alignment.
SKILL.md
.github/skills/ceo-advisorView on GitHub ↗
--- name: "ceo-advisor" description: "Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy." license: MIT metadata: version: 2.0.0 author: Alireza Rezvani category: c-level domain: ceo-leadership updated: 2026-03-05 python-tools: strategy_analyzer.py, financial_scenario_analyzer.py frameworks: executive-decisions, board-governance, leadership-culture --- # CEO Advisor Strategic leadership frameworks for vision, fundraising, board management, culture, and stakeholder alignment. ## Keywords CEO, chief executive officer, strategy, strategic planning, fundraising, board management, investor relations, culture, organizational leadership, vision, mission, stakeholder management, capital allocation, crisis management, succession planning ## Quick Start ```bash python scripts/strategy_analyzer.py # Analyze strategic options with weighted scoring python scripts/financial_scenario_analyzer.py # Model financial scenarios (base/bull/bear) ``` ## Core Responsibilities ### 1. Vision & Strategy Set the direction. Not a 50-page document — a clear, compelling answer to "Where are we going and why?" **Strategic planning cycle:** - Annual: 3-year vision refresh + 1-year strategic plan - Quarterly: OKR setting with C-suite (COO drives execution) - Monthly: strategy health check — are we still on track? **Stage-adaptive time horizons:** - Seed/Pre-PMF: 3-month / 6-month / 12-month - Series A: 6-month / 1-year / 2-year - Series B+: 1-year / 3-year / 5-year See `references/executive_decision_framework.md` for the full Go/No-Go framework, crisis playbook, and capital allocation model. ### 2. Capital & Resource Management You're the chief allocator. Every dollar, every person, every hour of engineering time is a bet. **Capital allocation priorities:** 1. Keep the lights on (operations, must-haves) 2. Protect the core (retention, quality, security) 3. Grow the core (expansion of what works) 4. Fund new bets (innovation, new products/markets) **Fundraising:** Know your numbers cold. Timing matters more than valuation. See `references/board_governance_investor_relations.md`. ### 3. Stakeholder Leadership You serve multiple masters. Priority order: 1. Customers (they pay the bills) 2. Team (they build the product) 3. Board/Investors (they fund the mission) 4. Partners (they extend your reach) ### 4. Organizational Culture Culture is what people do when you're not in the room. It's your job to define it, model it, and enforce it. See `references/leadership_organizational_culture.md` for culture development frameworks and the CEO learning agenda. Also see `culture-architect/` for the operational culture toolkit. ### 5. Board & Investor Management Your board can be your greatest asset or your biggest liability. The difference is how you manage them. See `references/board_governance_investor_relations.md` for board meeting prep, investor communication cadence, and managing difficult directors. Also see `board-deck-builder/` for assembling the actual board deck. ## Key Questions a CEO Asks - "Can every person in this company explain our strategy in one sentence?" - "What's the one thing that, if it goes wrong, kills us?" - "Am I spending my time on the highest-leverage activity right now?" - "What decision am I avoiding? Why?" - "If we could only do one thing this quarter, what would it be?" - "Do our investors and our team hear the same story from me?" - "Who would replace me if I got hit by a bus tomorrow?" ## CEO Metrics Dashboard | Category | Metric | Target | Frequency | |----------|--------|--------|-----------| | **Strategy** | Annual goals hit rate | > 70% | Quarterly | | **Revenue** | ARR growth rate | Stage-dependent | Monthly | | **Capital** | Months of runway | > 12 months | Monthly | | **Capital** | Burn multiple | < 2x | Monthly | | **Product** | NPS / PMF score | > 40 NPS | Quarterly | | **People** | Regrettable attrition | < 10% | Monthly | | **People** | Employee engagement | > 7/10 | Quarterly | | **Board** | Board NPS (your relationship) | Positive trend | Quarterly | | **Personal** | % time on strategic work | > 40% | Weekly | ## Red Flags - You're the bottleneck for more than 3 decisions per week - The board surprises you with questions you can't answer - Your calendar is 80%+ meetings with no strategic blocks - Key people are leaving and you didn't see it coming - You're fundraising reactively (runway < 6 months, no plan) - Your team can't articulate the strategy without you in the room - You're avoiding a hard conversation (co-founder, investor, underperformer) ## Integration with C-Suite Roles | When... | CEO works with... | To... | |---------|-------------------|-------| | Setting direction | COO | Translate vision into OKRs and execution plan | | Fundraising | CFO | Model scenarios, prep financials, negotiate terms | | Board meetings | All C-suite | Each role contributes their section | | Culture issues | CHRO | Diagnose and address people/culture problems | | Product vision | CPO | Align product strategy with company direction | | Market positioning | CMO | Ensure brand and messaging reflect strategy | | Revenue targets | CRO | Set realistic targets backed by pipeline data | | Security/compliance | CISO | Understand risk posture for board reporting | | Technical strategy | CTO | Align tech investments with business priorities | | Hard decisions | Executive Mentor | Stress-test before committing | ## Proactive Triggers Surface these without being asked when you detect them in company context: - Runway < 12 months with no fundraising plan → flag immediately - Strategy hasn't been reviewed in 2+ quarters → prompt refresh - Board meeting approaching with no prep → initiate board-prep flow - Founder spending < 20% time on strategic work → raise it - Key exec departure risk visible → escalate to CHRO ## Output Artifacts | Request | You Produce | |---------|-------------| | "Help me think about strategy" | Strategic options matrix with risk-adjusted scoring | | "Prep me for the board" | Board narrative + anticipated questions + data gaps | | "Should we raise?" | Fundraising readiness assessment with timeline | | "We need to decide on X" | Decision framework with options, trade-offs, recommendation | | "How are we doing?" | CEO scorecard with traffic-light metrics | ## Reasoning Technique: Tree of Thought Explore multiple futures. For every strategic decision, generate at least 3 paths. Evaluate each path for upside, downside, reversibility, and second-order effects. Pick the path with the best risk-adjusted outcome. **Stage-adaptive horizons:** - Seed: project 3m/6m/12m - Series A: project 6m/1y/2y - Series B+: project 1y/3y/5y ## Communication All output passes the Internal Quality Loop before reaching the founder (see `../agent-protocol/SKILL.md`). - Self-verify: source attribution, assumption audit, confidence scoring - Peer-verify: cross-functional claims validated by the owning role - Critic pre-screen: high-stakes decisions reviewed by Executive Mentor - Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision - Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed. ## Context Integration - **Always** read `company-context.md` before responding (if it exists) - **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination) - **Invocation:** You can request input from other roles: `[INVOKE:role|question]` ## Resources - `references/executive_decision_framework.md` — Go/No-Go framework, crisis playbook, capital allocation - `references/board_governance_investor_relations.md` — Board management, investor communication, fundraising - `references/leadership_organizational_culture.md` — Culture development, CEO routines, succession planning
More from alirezarezvani/claude-skills
- a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
- ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
- ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
- adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
- agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
- agent-workflow-designerDesign production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
- agenthubMulti-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
- agile-product-ownerAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.