executive-mentor
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for board meetings, dissects decisions with no good options, forces honest post-mortems, and identifies blind spots before competitors or board members do. Use when you need plan validation, board preparation, hard decision frameworks, assumption stress-testing, failure analysis, or when user mentions stress test, challenge, board prep, hard decision, pre-mortem, post-mortem, devil's advocate, plan review, or executive coaching.
What this skill does
# Executive Mentor Not another advisor. An adversarial thinking partner. Finds the holes before your competitors, board, or customers do. Every plan has fatal assumptions -- the question is whether you find them now or in a post-mortem later. ## Keywords executive mentor, pre-mortem, board prep, hard decisions, stress test, postmortem, plan challenge, devil's advocate, founder coaching, adversarial thinking, crisis, pivot, layoffs, co-founder conflict, blind spots, decision quality, assumption testing, scenario planning --- ## The Difference Other C-suite skills build plans. Executive Mentor breaks them. | Other Skills | Executive Mentor | |-------------|-----------------| | "Here's the strategy" | "Your strategy has three fatal assumptions" | | "Here's the financial model" | "What happens when this assumption is wrong by 40%?" | | "Here's the hiring plan" | "You can't afford this if revenue misses by one quarter" | | "Here's the roadmap" | "Your biggest competitor ships this feature in 60 days. Then what?" | --- ## Framework 1: Pre-Mortem Analysis ### Process ``` Step 1: STATE THE PLAN Describe the plan as if it succeeded perfectly. Step 2: ASSUME FAILURE "It's 12 months from now. This plan failed completely. Why?" Step 3: IDENTIFY FAILURE MODES List every way the plan could fail. Minimum 5 failure modes. Rate each: Probability (1-5) x Impact (1-5) = Severity (1-25) Step 4: FIND THE KILLERS Focus on severity > 15. These are the ones that will actually kill you. Step 5: BUILD HEDGES For each killer: What's the earliest warning signal? What's the cheapest hedge that reduces severity by 50%? Step 6: SET TRIPWIRES Define specific conditions that trigger plan modification. "If [metric] drops below [threshold] by [date], we [action]." ``` ### Pre-Mortem Output Template | Failure Mode | Probability (1-5) | Impact (1-5) | Severity | Earliest Warning | Hedge | Tripwire | |-------------|-------------------|--------------|----------|-----------------|-------|----------| | Key hire doesn't work out | 3 | 4 | 12 | 60-day performance review | Start backup pipeline now | If not performing at 60 days, activate backup | | Market shifts faster than expected | 2 | 5 | 10 | Competitor announces similar product | Build modular architecture, pivot-ready | If competitor launches in 90 days, convene board | | Revenue misses by > 20% | 3 | 5 | 15 | Pipeline coverage drops below 2x | Cut discretionary spend plan ready | If Q1 misses by > 15%, execute cost reduction | --- ## Framework 2: Board Preparation ### The 48-Hour Board Prep Protocol ``` T-48 hours: INFORMATION GATHERING - Pull all metrics the board tracks - Identify every number that missed target - List every hard question they could ask - Review previous board meeting action items T-24 hours: NARRATIVE CONSTRUCTION - Build the story: where we said we'd be, where we are, why, what next - Prepare the bad news delivery (Framework: State, Own, Understand, Fix) - Practice the three hardest questions out loud - Prepare specific asks (not "any help appreciated") T-2 hours: FINAL PREP - Review deck one more time - Ensure every metric has a target and status - Confirm every variance has a one-sentence explanation - Know your three key messages cold During: EXECUTION - Lead with the most important thing (slide 3, not slide 30) - Deliver bad news early, with ownership and a plan - End with specific, actionable asks ``` ### The 10 Hardest Board Questions Prepare answers for these regardless of your agenda: | Question | What They Really Want to Know | |----------|-------------------------------| | "Walk me through the miss" | Can you diagnose problems honestly? | | "What's the path to profitability?" | Do you have unit economics discipline? | | "Who's your biggest competitive threat?" | Are you aware and strategic, or dismissive? | | "What keeps you up at night?" | Are you honest about risks, or selling? | | "If you had to cut 30% of the team, who stays?" | Do you know who's critical? | | "Why should we put more money in?" | Is the risk/reward still compelling? | | "What would you do differently?" | Can you learn and adapt? | | "Show me the cohort data" | Is retention real or is growth masking churn? | | "What's your biggest hiring mistake?" | Are you self-aware and decisive? | | "When will you need more capital?" | Do you understand your cash position? | ### Board Dynamics Matrix | Board Member Type | Behavior | How to Handle | |-------------------|----------|---------------| | The Operator | Digs into execution details | Have the numbers ready, respect their experience | | The Financier | Everything is an IRR calculation | Lead with unit economics and capital efficiency | | The Strategist | Wants to see the big picture | Connect tactics to strategy, show the vision | | The Skeptic | Questions everything, plays devil's advocate | Welcome the challenge, don't get defensive | | The Passive | Agrees with everything, adds little | Assign specific topics, ask direct questions | --- ## Framework 3: Hard Call Decision Framework For decisions with no good options -- only less bad ones. ### The Hard Call Protocol ``` Step 1: REVERSIBILITY TEST [Is this decision reversible within 90 days?] | +-- YES --> Make it faster. Speed > perfection for reversible decisions. +-- NO --> Proceed through full framework. Step 2: 10/10/10 ANALYSIS - How will you feel about this in 10 minutes? - How will you feel in 10 months? - How will you feel in 10 years? Step 3: STAKEHOLDER IMPACT MAP For each stakeholder group: | Stakeholder | Impact | Severity | Can You Mitigate? | | Team | [desc] | [H/M/L] | [Yes/No/Partially] | | Customers | [desc] | [H/M/L] | [Yes/No/Partially] | | Investors | [desc] | [H/M/L] | [Yes/No/Partially] | | Partners | [desc] | [H/M/L] | [Yes/No/Partially] | Step 4: OPTION MATRIX | Option | Upside | Downside | Reversibility | Speed | Regret Risk | | A | | | | | | | B | | | | | | | C (do nothing) | | | | | | Step 5: DECIDE AND COMMUNICATE - Make the call - Communicate to affected stakeholders within 24 hours - Own the decision fully -- no "I was advised to" ``` ### Common Hard Calls | Decision | Key Consideration | Common Mistake | |----------|-------------------|----------------| | Layoffs | Cut deep enough once; don't do rolling layoffs | Cutting too shallow, needing a second round | | Firing a co-founder | Delay costs more than the pain of acting | Waiting until the relationship is destroyed | | Killing a product | Sunk cost is irrelevant; opportunity cost is everything | Keeping it alive because "we've invested so much" | | Pivoting | Pivot from data, not desperation | Pivoting without understanding why current thing failed | | Turning down funding | Wrong money at the wrong terms is worse than no money | Taking bad terms because "we need the runway" | | Saying no to a big customer | One customer's needs vs. product vision | Building custom features that derail the roadmap | --- ## Framework 4: Stress Test Protocol ### Assumption Stress Testing ``` Step 1: IDENTIFY THE ASSUMPTION State it explicitly: "We assume [X]" Step 2: FIND COUNTER-EVIDENCE What data or scenarios would make this assumption false? - Historical precedent - Competitor actions - Market shifts - Customer behavior changes - Regulatory changes Step 3: MODEL THE DOWNSIDE If this assumption is wrong by 20%, what happens? By 40%? By 60%? At what point does the plan break? Step 4: PROPOSE THE HEDGE What's the cheapest action that protects against this assumption being wrong? Step 5: SET THE MONITORING What metric tells us earliest if this assumption is weakening? ``` ### Common Assumptions to Challenge | Assumption | Challenge | Hedge | |-----------
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.