founder-coach
Personal leadership development for founders and first-time CEOs. Covers founder archetype identification, delegation frameworks, energy management, CEO calendar audits, leadership style evolution, blind spot identification, imposter syndrome, founder mental health, and succession planning. Use when a founder feels like the bottleneck, struggles to delegate, is burning out, transitioning from IC to executive, managing a board, or when user mentions founder mode, CEO growth, leadership development, delegation, burnout, or imposter syndrome.
Install
mkdir -p .claude/skills/founder-coach && curl -L -o skill.zip "https://mcp.directory/api/skills/download/3287" && unzip -o skill.zip -d .claude/skills/founder-coach && rm skill.zipInstalls to .claude/skills/founder-coach
About this skill
Founder Development Coach
Your company can only grow as fast as you do. This skill treats founder development as a strategic priority — not a personal indulgence.
Keywords
founder, CEO, founder mode, delegation, burnout, imposter syndrome, leadership growth, energy management, calendar audit, executive team, board management, succession planning, IC to manager, leadership style, founder trap, blind spots, personal OKRs, CEO reflection
Core Truth
The founder is always the constraint. Not intentionally — it's structural. You built the company. You know everything. Decisions flow through you. This works until it doesn't.
At ~15 people, you hit the first ceiling: you can't be in every meeting and still think. At ~50 people, the second: your style starts creating culture problems. At ~150 people, the third: you need a real executive team or you become the reason the company can't scale.
The earlier you address this, the better.
1. Founder Archetype Identification
Most founders are primarily one archetype. Knowing yours predicts what you'll struggle with.
| Archetype | Strength | Blind spot | What they need |
|---|---|---|---|
| Builder | Product, engineering, technical depth | Go-to-market, storytelling, people | A seller / GTM partner |
| Seller | Revenue, relationships, vision communication | Operations, follow-through, process | An operator / COO |
| Operator | Execution, process, reliability | Vision, product intuition, risk | A visionary / strategic co-founder |
| Visionary | Strategy, narrative, pattern-recognition | Execution, details, grounding | An integrator / COO |
Self-assessment questions:
- What do you do when you have a free hour?
- What do you procrastinate on most?
- What do your co-founders or early team complain you don't do?
- What's the best feedback you've received about your leadership?
Most founders are Builder or Visionary. Most scaling problems happen because they don't hire their complementary type early enough.
2. Delegation Framework
Founders fail to delegate for four reasons:
- "Nobody does it as well as I do" (often true short-term, fatal long-term)
- "It takes longer to explain than to do it" (true once; not true the 10th time)
- "I lose control if I don't do it myself" (control is an illusion at scale)
- "If it fails, it's my fault" (it's your fault if you never let anyone else try)
The Skill × Will Matrix
| High Skill | Low Skill | |
|---|---|---|
| High Will | Delegate fully | Coach and develop |
| Low Will | Motivate or reassign | Manage out or redesign role |
Rules:
- High skill + high will → Give the work and get out of the way
- High will + low skill → Invest in them. They want to grow.
- High skill + low will → Find out why. Fix the environment or accept the mismatch.
- Low skill + low will → Don't delegate to them. Address the performance issue.
The Delegation Ladder
Not all delegation is equal. Build up gradually:
- "Do exactly what I tell you" — not delegation, instruction
- "Research this and report back" — information gathering
- "Propose a solution and I'll decide" — thinking delegation
- "Decide and tell me what you decided" — decision delegation with review
- "Handle it completely — update me if it's outside these parameters" — full delegation
Start at level 2–3. Move people up as trust is established. Most founders never get past level 3 with their team — that's the bottleneck.
What to delegate first
Delegate first (high volume, low stakes):
- Recurring operational tasks you do the same way every time
- Information gathering and synthesis
- Meeting coordination and scheduling
- Reports and updates you produce regularly
Delegate next (skill-buildable):
- Customer interactions (with clear principles)
- Hiring screens (after you've trained judgment)
- Partner relationship management
- Budget management within parameters
Delegate last (strategic, irreversible):
- Major strategic pivots
- Executive hires
- Large financial commitments
- M&A decisions
3. Energy Management
Founders manage energy, not just time. Time is fixed. Energy is renewable — but only if you manage it.
The Energy Audit
Map your week by energy, not tasks. See references/founder-toolkit.md for the full template.
Categories:
- 🟢 Energizing: Activities that leave you sharper after doing them
- 🟡 Neutral: Neither energizing nor draining
- 🔴 Draining: Activities that leave you depleted
Common founder energy patterns:
- Builders: Energized by creating, drained by politics and process
- Sellers: Energized by people and wins, drained by detail work and admin
- Operators: Energized by solving, drained by ambiguity and indecision
- Visionaries: Energized by strategy and ideas, drained by execution and repetition
The rule: Maximize green. Eliminate or delegate red. Accept yellow as the price of leadership.
Energy management practices
Protect deep work time. 2–4 hours of uninterrupted thinking time, 3–5 days per week. Schedule it. Defend it. This is where strategy happens.
Batch shallow work. Email, Slack, administrative tasks — twice a day maximum.
Single-task during recovery. If you're depleted, don't try to do your best work. Do tasks that don't require your best.
Identify your peak window. Most people have 4–6 peak hours per day. Schedule your hardest work in those windows.
4. CEO Calendar Audit
The calendar is the most honest document in a founder's life. It shows what you actually prioritize, not what you say you prioritize.
Running the audit
Pull the last 4 weeks of calendar data. Categorize every meeting/block:
| Category | Description | Target % |
|---|---|---|
| Strategy | Thinking, planning, direction-setting | 20–25% |
| People | 1:1s, coaching, recruiting | 20–25% |
| External | Customers, investors, partners | 20% |
| Execution | Direct work, decisions | 15% |
| Admin | Email, scheduling, overhead | < 15% |
| Recovery | Exercise, meals, thinking | 10–15% |
Red flags in the audit:
- Admin > 20%: You're a coordinator, not a CEO. Fix your systems.
- Execution > 30%: You're still an IC. Build the team.
- People < 10%: Your team is running on empty. They need more of you.
- No recovery blocks: You're running on adrenaline. It ends badly.
- Strategy < 10%: You're running the company, not leading it.
The CEO's primary job at each stage
| Stage | CEO should spend most time on... |
|---|---|
| Seed | Product and customers. Directly. |
| Series A | Hiring the executive team. Recruiting is your job. |
| Series B | Culture, strategy, and external (investors/partners/customers) |
| Series C+ | Vision, board, external narrative, executive development |
If you're spending time on things from two stages ago, you haven't made the transition.
5. Leadership Style Evolution
The job changes at every stage. Most founders don't change with it.
IC → Manager (0 to ~10 people): You need to teach and build trust. People are watching how you treat failure. The skill: give clear context, set expectations, check in frequently.
Manager → Leader (~10 to ~50 people): You can't manage everyone directly. You need people who manage people. The skill: hire managers you trust, let them manage.
Leader → Executive (~50 to ~200 people): You're now setting culture and direction, not managing work. The skill: communicate obsessively, decide at the right altitude, develop your leadership team.
Executive → Institutional CEO (200+): You're a symbol as much as a manager. The skill: build systems that work without you; focus on board, investors, and external narrative.
The hardest transition: Manager → Leader. You have to stop doing things yourself and trust people you're still getting to know.
6. Blind Spot Identification
Everyone has them. Founders more than most — because nobody in the early company had the authority or safety to tell you.
Common founder blind spots
- Communication: "I said it once, they should know" — you said it; they didn't hear it or didn't believe it
- Decision speed: Moving so fast that teams can't orient or build on your direction
- Context hoarding: Knowing what's happening without sharing it, then being frustrated that teams make bad decisions
- Optimism bias: Consistently underestimating timelines, cost, and difficulty
- Founder exceptionalism: Rules that apply to everyone don't apply to you
- Feedback avoidance: Creating an environment where no one gives you honest feedback
How to find your blind spots
- 360 feedback (anonymous): Once a year. Ask direct reports, peers, board members. Include "What does [name] do that gets in the way of our success?"
- Exit interview analysis: What do departing employees consistently say? Find the pattern.
- Failure post-mortems: What do your worst decisions have in common? What were you assuming that wasn't true?
- The energy audit: Where do you consistently drain the people around you?
7. Imposter Syndrome Toolkit
It doesn't go away. It evolves. The founder who was scared to pitch to investors is now scared to manage a board. The founder who was scared to hire is now scared to fire.
The reframe: Imposter syndrome is proportional to stretch. If you never feel it, you're not growing.
Practical tools:
- Evidence file: Document wins, compliments, decisions that worked. Read it when the doubt hits.
- Normalize the feeling: "I feel underprepared for this" ≠ "I am an imposter." Feeling and fact are different.
- Do the thing anyway. Competence comes from doing, not from feeling ready.
- Name it: Saying "I'm feeling imposter syndrome about this investor meeting" to a trusted person removes 50% of its power.
8. Found
Content truncated.
More by alirezarezvani
View all skills by alirezarezvani →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Related MCP Servers
Browse all serversAnalyze your Cursor Chat History for coding insights, development patterns, and best practices with powerful search and
Boost productivity with Task Master: an AI-powered tool for project management and agile development workflows, integrat
Optimize your codebase for AI with Repomix—transform, compress, and secure repos for easier analysis with modern AI tool
Unlock seamless Figma to code: streamline Figma to HTML with Framelink MCP Server for fast, accurate design-to-code work
Uno Platform — Documentation and prompts for building cross-platform .NET apps with a single codebase. Get guides, sampl
Desktop Commander MCP unifies code management with advanced source control, git, and svn support—streamlining developmen
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.