Leadership coaching and management strategy for startup founders and CEOs.

Install

mkdir -p .claude/skills/founder-coach && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3287" && unzip -o skill.zip -d .claude/skills/founder-coach && rm skill.zip

Installs to .claude/skills/founder-coach

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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.
545 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • Identify founder archetypes
  • Implement delegation frameworks
  • Conduct CEO calendar audits
  • Manage founder energy levels
  • Identify leadership blind spots

How it works

It applies leadership frameworks to assess the founder's current role, energy, and delegation habits against their company stage.

Inputs & outputs

You give it
Founder leadership challenge or burnout symptoms
You get back
Leadership development plan and actionable coaching advice

When to use founder-coach

  • Evaluate CEO calendar
  • Identify leadership blind spots
  • Set up delegation frameworks

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.

ArchetypeStrengthBlind spotWhat they need
BuilderProduct, engineering, technical depthGo-to-market, storytelling, peopleA seller / GTM partner
SellerRevenue, relationships, vision communicationOperations, follow-through, processAn operator / COO
OperatorExecution, process, reliabilityVision, product intuition, riskA visionary / strategic co-founder
VisionaryStrategy, narrative, pattern-recognitionExecution, details, groundingAn 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:

  1. "Nobody does it as well as I do" (often true short-term, fatal long-term)
  2. "It takes longer to explain than to do it" (true once; not true the 10th time)
  3. "I lose control if I don't do it myself" (control is an illusion at scale)
  4. "If it fails, it's my fault" (it's your fault if you never let anyone else try)

The Skill × Will Matrix

High SkillLow Skill
High WillDelegate fullyCoach and develop
Low WillMotivate or reassignManage 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:

  1. "Do exactly what I tell you" — not delegation, instruction
  2. "Research this and report back" — information gathering
  3. "Propose a solution and I'll decide" — thinking delegation
  4. "Decide and tell me what you decided" — decision delegation with review
  5. "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:

CategoryDescriptionTarget %
StrategyThinking, planning, direction-setting20–25%
People1:1s, coaching, recruiting20–25%
ExternalCustomers, investors, partners20%
ExecutionDirect work, decisions15%
AdminEmail, scheduling, overhead< 15%
RecoveryExercise, meals, thinking10–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

StageCEO should spend most time on...
SeedProduct and customers. Directly.
Series AHiring the executive team. Recruiting is your job.
Series BCulture, 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

  1. 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?"
  2. Exit interview analysis: What do departing employees consistently say? Find the pattern.
  3. Failure post-mortems: What do your worst decisions have in common? What were you assuming that wasn't true?
  4. 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.

When not to use it

  • When the user is not a founder or first-time CEO
  • When the issue is purely technical rather than leadership-related

Limitations

  • Requires founder self-assessment data
  • Dependent on user honesty regarding calendar and energy

How it compares

It treats founder development as a structural business constraint rather than a personal coaching exercise.

Compared to similar skills

founder-coach side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
founder-coach (this skill)13moNo flagsAdvanced
archon99moReviewIntermediate
linear102moNo flagsBeginner
zapier-workflows118moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

More by alirezarezvani

View all by alirezarezvani

ma-playbook

alirezarezvani

M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.

39122

ad-creative

alirezarezvani

When 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.

3395

content-trend-researcher

alirezarezvani

Advanced content and topic research skill that analyzes trends across Google Analytics, Google Trends, Substack, Medium, Reddit, LinkedIn, X, blogs, podcasts, and YouTube to generate data-driven article outlines based on user intent analysis

30126

cold-email

alirezarezvani

When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).

2971

content-humanizer

alirezarezvani

Makes AI-generated content sound genuinely human — not just cleaned up, but alive. Use when content feels robotic, uses too many AI clichés, lacks personality, or reads like it was written by committee. Triggers: 'this sounds like AI', 'make it more human', 'add personality', 'it feels generic', 'sounds robotic', 'fix AI writing', 'inject our voice'. NOT for initial content creation (use content-production). NOT for SEO optimization (use content-production Mode 3).

2251

aws-solution-architect

alirezarezvani

Design AWS architectures for startups using serverless patterns and IaC templates. Use when asked to design serverless architecture, create CloudFormation templates, optimize AWS costs, set up CI/CD pipelines, or migrate to AWS. Covers Lambda, API Gateway, DynamoDB, ECS, Aurora, and cost optimization.

2047

You might also like

archon

coleam00

Interactive Archon integration for knowledge base and project management via REST API. On first use, asks for Archon host URL. Use when searching documentation, managing projects/tasks, or querying indexed knowledge. Provides RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning. Always try Archon first for external documentation and knowledge retrieval before using other sources.

9140

linear

lobehub

Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.

10117

zapier-workflows

davila7

Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.

11101

attio-skill-generator

kesslerio

Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.

7100

github-manage

matteocervelli

Manage operations concerning GitHub on behalf of user

693

cto-engineering-metrics

rinaldofesta

Expert methodology for defining, tracking, and interpreting engineering performance metrics including DORA, team health, productivity, and executive reporting.

585

Search skills

Search the agent skills registry