artifacts/bundle/skills/c-level-advisor/founder-coach/SKILL.md
# 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.
npx skillsauth add neekware/ehayeskills artifacts/bundle/skills/c-level-advisor/founder-coachInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Your company can only grow as fast as you do. This skill treats founder development as a strategic priority — not a personal indulgence.
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
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.
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:
Most founders are Builder or Visionary. Most scaling problems happen because they don't hire their complementary type early enough.
Founders fail to delegate for four reasons:
| | High Skill | Low Skill | | ------------- | -------------------- | --------------------------- | | High Will | Delegate fully | Coach and develop | | Low Will | Motivate or reassign | Manage out or redesign role |
Rules:
Not all delegation is equal. Build up gradually:
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.
Delegate first (high volume, low stakes):
Delegate next (skill-buildable):
Delegate last (strategic, irreversible):
Founders manage energy, not just time. Time is fixed. Energy is renewable — but only if you manage it.
Map your week by energy, not tasks. See references/founder-toolkit.md for the full template.
Categories:
Common founder energy patterns:
The rule: Maximize green. Eliminate or delegate red. Accept yellow as the price of leadership.
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.
The calendar is the most honest document in a founder's life. It shows what you actually prioritize, not what you say you prioritize.
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:
| 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.
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.
Everyone has them. Founders more than most — because nobody in the early company had the authority or safety to tell you.
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:
Burnout isn't weakness. It's a predictable outcome of high-demand + low-recovery + no control over inputs.
Early: Irritability, difficulty sleeping, decisions feel harder than they should, loss of enthusiasm for the mission. Mid: Physical symptoms (headaches, illness), cynicism about the company, social withdrawal, all tasks feel equally important (priority paralysis). Late: Can't function, decisions have stopped, team notices before you do.
If you're in late burnout: Stop performing. Get support. The company needs a functioning founder more than it needs a martyred one.
Paul Graham's "Founder Mode" essay made the case that great founders stay deeply involved in operations — skip middle management and go direct. It resonated because it's sometimes true.
When founder mode helps:
When founder mode hurts:
The test: Are you going deep because the situation requires it, or because you're uncomfortable with the loss of control? The first is leadership. The second is the trap.
Building a company that works without you is not disloyalty — it's the ultimate expression of leadership.
Succession is not just about exit. It's about resilience. What happens if you're sick? On sabbatical? Acquired?
Succession readiness levels:
Most founders are at Level 0. Level 2 is a reasonable target. Level 3 is a strategic asset.
references/leadership-growth.md — Maxwell levels, situational leadership, founder-to-CEO transitionreferences/founder-toolkit.md — Weekly reflection, energy audit, delegation matrix, 1:1 templatesCreator: Alireza Rezvani License: MIT Source Repo:
neekware/ehaye-skillsSource Bucket:c-level-advisorOriginal Path:c-level-advisor/founder-coach
tools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski