Files
claude-skills-reference/c-level-advisor/founder-coach/references/founder-toolkit.md
Alireza Rezvani 466aa13a7b feat: C-Suite expansion — 8 new executive advisory roles (2→10) (#264)
* feat: C-Suite expansion — 8 new executive advisory roles

Add COO, CPO, CMO, CFO, CRO, CISO, CHRO advisors and Executive Mentor.
Expands C-level advisory from 2 to 10 roles with 74 total files.

Each role includes:
- SKILL.md (lean, <5KB, ~1200 tokens for context efficiency)
- Reference docs (loaded on demand, not at startup)
- Python analysis scripts (stdlib only, runnable CLI)

Executive Mentor features /em: slash commands (challenge, board-prep,
hard-call, stress-test, postmortem) with devil's advocate agent.

21 Python tools, 24 reference frameworks, 28,379 total lines.
All SKILL.md files combined: ~17K tokens (8.5% of 200K context window).

Badge: 88 → 116 skills

* feat: C-Suite orchestration layer + 18 complementary skills

ORCHESTRATION (new):
- cs-onboard: Founder interview → company-context.md
- chief-of-staff: Routing, synthesis, inter-agent orchestration
- board-meeting: 6-phase multi-agent deliberation protocol
- decision-logger: Two-layer memory (raw transcripts + approved decisions)
- agent-protocol: Inter-agent invocation with loop prevention
- context-engine: Company context loading + anonymization

CROSS-CUTTING CAPABILITIES (new):
- board-deck-builder: Board/investor update assembly
- scenario-war-room: Cascading multi-variable what-if modeling
- competitive-intel: Systematic competitor tracking + battlecards
- org-health-diagnostic: Cross-functional health scoring (8 dimensions)
- ma-playbook: M&A strategy (acquiring + being acquired)
- intl-expansion: International market entry frameworks

CULTURE & COLLABORATION (new):
- culture-architect: Values → behaviors, culture code, health assessment
- company-os: EOS/Scaling Up operating system selection + implementation
- founder-coach: Founder development, delegation, blind spots
- strategic-alignment: Strategy cascade, silo detection, alignment scoring
- change-management: ADKAR-based change rollout framework
- internal-narrative: One story across employees/investors/customers

UPGRADES TO EXISTING ROLES:
- All 10 roles get reasoning technique directives
- All 10 roles get company-context.md integration
- All 10 roles get board meeting isolation rules
- CEO gets stage-adaptive temporal horizons (seed→C)

Key design decisions:
- Two-layer memory prevents hallucinated consensus from rejected ideas
- Phase 2 isolation: agents think independently before cross-examination
- Executive Mentor (The Critic) sees all perspectives, others don't
- 25 Python tools total (stdlib only, no dependencies)

52 new files, 10 modified, 10,862 new lines.
Total C-suite ecosystem: 134 files, 39,131 lines.

* fix: connect all dots — Chief of Staff routes to all 28 skills

- Added complementary skills registry to routing-matrix.md
- Chief of Staff SKILL.md now lists all 28 skills in ecosystem
- Added integration tables to scenario-war-room and competitive-intel
- Badge: 116 → 134 skills
- README: C-Level Advisory count 10 → 28

Quality audit passed:
 All 10 roles: company-context, reasoning, isolation, invocation
 All 6 phases in board meeting
 Two-layer memory with DO_NOT_RESURFACE
 Loop prevention (no self-invoke, max depth 2, no circular)
 All /em: commands present
 All complementary skills cross-reference roles
 Chief of Staff routes to every skill in ecosystem

* refactor: CEO + CTO advisors upgraded to C-suite parity

Both roles now match the structural standard of all new roles:
- CEO: 11.7KB → 6.8KB SKILL.md (heavy content stays in references)
- CTO: 10KB → 7.2KB SKILL.md (heavy content stays in references)

Added to both:
- Integration table (who they work with and when)
- Key diagnostic questions
- Structured metrics dashboard table
- Consistent section ordering (Keywords → Quick Start → Responsibilities → Questions → Metrics → Red Flags → Integration → Reasoning → Context)

CEO additions:
- Stage-adaptive temporal horizons (seed=3m/6m/12m → B+=1y/3y/5y)
- Cross-references to culture-architect and board-deck-builder

CTO additions:
- Key Questions section (7 diagnostic questions)
- Structured metrics table (DORA + debt + team + architecture + cost)
- Cross-references to all peer roles

All 10 roles now pass structural parity:  Keywords  QuickStart  Questions  Metrics  RedFlags  Integration

* feat: add proactive triggers + output artifacts to all 10 roles

Every C-suite role now specifies:
- Proactive Triggers: 'surface these without being asked' — context-driven
  early warnings that make advisors proactive, not reactive
- Output Artifacts: concrete deliverables per request type (what you ask →
  what you get)

CEO: runway alerts, board prep triggers, strategy review nudges
CTO: deploy frequency monitoring, tech debt thresholds, bus factor flags
COO: blocker detection, scaling threshold warnings, cadence gaps
CPO: retention curve monitoring, portfolio dog detection, research gaps
CMO: CAC trend monitoring, positioning gaps, budget staleness
CFO: runway forecasting, burn multiple alerts, scenario planning gaps
CRO: NRR monitoring, pipeline coverage, pricing review triggers
CISO: audit overdue alerts, compliance gaps, vendor risk
CHRO: retention risk, comp band gaps, org scaling thresholds
Executive Mentor: board prep triggers, groupthink detection, hard call surfacing

This transforms the C-suite from reactive advisors into proactive partners.

* feat: User Communication Standard — structured output for all roles

Defines 3 output formats in agent-protocol/SKILL.md:

1. Standard Output: Bottom Line → What → Why → How to Act → Risks → Your Decision
2. Proactive Alert: What I Noticed → Why It Matters → Action → Urgency (🔴🟡)
3. Board Meeting: Decision Required → Perspectives → Agree/Disagree → Critic → Action Items

10 non-negotiable rules:
- Bottom line first, always
- Results and decisions only (no process narration)
- What + Why + How for every finding
- Actions have owners and deadlines ('we should consider' is banned)
- Decisions framed as options with trade-offs
- Founder is the highest authority — roles recommend, founder decides
- Risks are concrete (if X → Y, costs $Z)
- Max 5 bullets per section
- No jargon without explanation
- Silence over fabricated updates

All 10 roles reference this standard.
Chief of Staff enforces it as a quality gate.
Board meeting Phase 4 uses the Board Meeting Output format.

* feat: Internal Quality Loop — verification before delivery

No role presents to the founder without passing verification:

Step 1: Self-Verification (every role, every time)
  - Source attribution: where did each data point come from?
  - Assumption audit: [VERIFIED] vs [ASSUMED] tags on every finding
  - Confidence scoring: 🟢 high / 🟡 medium / 🔴 low per finding
  - Contradiction check against company-context + decision log
  - 'So what?' test: every finding needs a business consequence

Step 2: Peer Verification (cross-functional)
  - Financial claims → CFO validates math
  - Revenue projections → CRO validates pipeline backing
  - Technical feasibility → CTO validates
  - People/hiring impact → CHRO validates
  - Skip for single-domain, low-stakes questions

Step 3: Critic Pre-Screen (high-stakes only)
  - Irreversible decisions, >20% runway impact, strategy changes
  - Executive Mentor finds weakest point before founder sees it
  - Suspicious consensus triggers mandatory pre-screen

Step 4: Course Correction (after founder feedback)
  - Approve → log + assign actions
  - Modify → re-verify changed parts
  - Reject → DO_NOT_RESURFACE + learn why
  - 30/60/90 day post-decision review

Board meeting contributions now require self-verified format with
confidence tags and source attribution on every finding.

* fix: resolve PR review issues 1, 4, and minor observation

Issue 1: c-level-advisor/CLAUDE.md — completely rewritten
  - Was: 2 skills (CEO, CTO only), dated Nov 2025
  - Now: full 28-skill ecosystem map with architecture diagram,
    all roles/orchestration/cross-cutting/culture skills listed,
    design decisions, integration with other domains

Issue 4: Root CLAUDE.md — updated all stale counts
  - 87 → 134 skills across all 3 references
  - C-Level: 2 → 33 (10 roles + 5 mentor commands + 18 complementary)
  - Tool count: 160+ → 185+
  - Reference count: 200+ → 250+

Minor observation: Documented plugin.json convention
  - Explained in c-level-advisor/CLAUDE.md that only executive-mentor
    has plugin.json because only it has slash commands (/em: namespace)
  - Other skills are invoked by name through Chief of Staff or directly

Also fixed: README.md 88+ → 134 in two places (first line + skills section)

* fix: update all plugin/index registrations for 28-skill C-suite

1. c-level-advisor/.claude-plugin/plugin.json — v2.0.0
   - Was: 2 skills, generic description
   - Now: all 28 skills listed with descriptions, all 25 scripts,
     namespace 'cs', full ecosystem description

2. .codex/skills-index.json — added 18 complementary skills
   - Was: 10 roles only
   - Now: 28 total c-level entries (10 roles + 6 orchestration +
     6 cross-cutting + 6 culture)
   - Each with full description for skill discovery

3. .claude-plugin/marketplace.json — updated c-level-skills entry
   - Was: generic 2-skill description
   - Now: v2.0.0, full 28-skill ecosystem description,
     skills_count: 28, scripts_count: 25

* feat: add root SKILL.md for c-level-advisor ClawHub package

---------

Co-authored-by: Leo <leo@openclaw.ai>
2026-03-06 01:35:08 +01:00

9.2 KiB

Founder Toolkit

Practical tools for founder self-management and leadership development.


1. Weekly CEO Reflection Template

15 minutes. Every Friday. No excuses.

This is the most important meeting of the week. You with yourself.

DATE: _______________

## This Week

**1. What was my most important contribution this week?**
(Not the longest meeting or the hardest problem — the thing that will matter in 90 days.)

_______________________________________________

**2. Where did I add the least value? Why was I involved?**
(Be honest. Where were you in the room out of habit, not necessity?)

_______________________________________________

**3. What should I have delegated but didn't?**
(Name the specific task and the person you could have delegated it to.)

_______________________________________________

**4. What decision am I avoiding? Why?**
(Fear of being wrong? Not enough information? Conflict avoidance?)

_______________________________________________

**5. What would I do differently this week if I could do it over?**
(One thing. Make it specific.)

_______________________________________________

## Next Week

**My one most important outcome for next week:**
_______________________________________________

**What will I stop doing / not start / protect myself from?**
_______________________________________________

2. Energy Audit Template

Map your week by energy, not tasks. Do this for one full work week.

Step 1: Time block mapping

For each 30-minute block in your week, record:

  • What you did
  • Energy level: 🟢 Energizing / 🟡 Neutral / 🔴 Draining
Monday:
08:00-08:30: __________________ [🟢/🟡/🔴]
08:30-09:00: __________________ [🟢/🟡/🔴]
09:00-09:30: __________________ [🟢/🟡/🔴]
... (continue through the day)

Step 2: Pattern analysis

After one week, categorize activities:

Activity type Energy level Total hours % of week
Customer calls
Investor meetings
Team 1:1s
Product decisions
Strategy/planning
Email/Slack
Recruiting
Financial review
External talks/events
Administrative tasks
Deep work/building
Recovery/breaks

Step 3: Optimization plan

Green activities to protect (min 40% of week):


Red activities to eliminate or delegate (target: < 15% of week):

  • Activity: __________________ → Delegate to: __________________
  • Activity: __________________ → Eliminate via: __________________

Your personal energy peak hours: I do my best thinking: _______ to _______ Schedule this time as: Protected deep work (no meetings)


3. Delegation Matrix

For every task you regularly do, run it through this matrix.

Assessment

Task Skill level needed My will to keep it Decision
High / Med / Low High / Med / Low Keep / Coach / Delegate / Kill

Delegation scoring

My Skill My Will Decision
High High Keep — this is your zone of genius
High Low Delegate — you can do it, but it drains you. Train someone.
Low High Develop — learn it or hire for it
Low Low Kill or outsource — why is this on your plate?

The 70% rule

If someone can do a task 70% as well as you, delegate it. Trying to get to 100% is a trap:

  • Their 70% will grow to 90% with practice
  • Your 30% extra effort costs more than the quality gap
  • You free up time for things only you can do

4. 1:1 Template for Direct Reports

Weekly or biweekly. 30 minutes. Their agenda, not yours.

DATE: _______________
PERSON: _______________

## Their Section (first 20 min)

**What's on their mind? (open the meeting with this)**
(No agenda from you first — let them lead)

**What are they working on? Where are they stuck?**

**What do they need from me?**

**Anything they wanted to raise but haven't had the chance to?**

## Your Section (last 10 min)

**Context to share (strategy, changes, what they should know):**

**Direct feedback to give (if any):**
- Be specific: "In Tuesday's meeting, when you [did X], the impact was [Y]"
- Make it actionable: "Next time, I'd suggest [Z]"

**Career/growth check-in (monthly, not every meeting):**
- How are they feeling about their growth?
- What do they want to be doing more of?
- What are they interested in that they're not currently doing?

## Follow-ups

| Commitment | Owner | Due |
|------------|-------|-----|
| | | |

Rules for effective 1:1s

  • Their agenda first. If you dominate with your updates, they stop bringing theirs.
  • No status updates. That's what tools are for. This time is for their thinking, blockers, and development.
  • Consistent time. Rescheduled 1:1s signal that they're not a priority.
  • Take notes. Review them before the next meeting. It signals that you listened.
  • Follow up on commitments. If you say "I'll get you that answer by Thursday," get it by Thursday.

5. Personal OKRs for the Founder

Most founders hold their team accountable to goals but have none themselves. Fix that.

Template: Quarterly Personal OKRs

Q[X] YYYY | FOUNDER OKRs

## My One Priority This Quarter
(The single most important thing I personally must accomplish)
_______________________________________________

## Objective 1: [Leadership Development]
What I'm trying to achieve: _______________________________________________

KR 1.1: [Measurable outcome by EoQ]
KR 1.2: [Measurable outcome by EoQ]
KR 1.3: [Measurable outcome by EoQ]

Progress check (mid-quarter): _______________________________________________

## Objective 2: [Delegation / Team Building]
What I'm trying to achieve: _______________________________________________

KR 2.1: [Measurable outcome by EoQ]
KR 2.2: [Measurable outcome by EoQ]

## Objective 3: [External Impact — Investors / Customers / Market]
What I'm trying to achieve: _______________________________________________

KR 3.1: [Measurable outcome by EoQ]
KR 3.2: [Measurable outcome by EoQ]

## The "Stop Doing" List (equally important)
Things I'm committing to stop doing this quarter:
- Stop: _______________________________________________
- Stop: _______________________________________________
- Stop: _______________________________________________

Personal OKR examples

Objective: Become a better coach, not just a decision-maker

  • KR: 90% of my direct reports can make their top 3 recurring decisions without me by EoQ
  • KR: In 1:1 reviews, 80% of team rates me as "helps me think through problems" vs "tells me what to do"
  • KR: Conduct quarterly 360 feedback session with all direct reports

Objective: Build investor trust before I need it

  • KR: Monthly investor updates sent within 5 days of month-end, every month this quarter
  • KR: 1:1 calls with each board member, once per quarter, outside of board meetings
  • KR: Create and share 3-year financial model with board by EoQ

Objective: Protect my energy and performance

  • KR: 3+ hours of protected deep work time per day, 4+ days per week
  • KR: Complete weekly CEO reflection every Friday (track: 0/13 weeks → 13/13)
  • KR: Zero email after 8pm, zero weekends unless explicit crisis

6. The "Stop Doing" List

The hardest list to make and the most valuable to keep.

Most founders have clear to-do lists. Few have stop-doing lists. The asymmetry is the problem.

The stop-doing audit

Things to stop doing immediately (decision you can make today):

  • Attending meetings you don't add value to
  • Being the default person for decisions that should be made by others
  • Redoing work that your team completed
  • Checking email/Slack during deep work blocks
  • Starting tasks you know you'll delegate partway through

Things to stop doing by delegating (need to train someone):




Things to stop doing by building systems:

  • Recurring manual tasks → automate
  • Recurring decisions → write decision criteria so others can decide
  • Recurring explanations → document once, reference always

The decision filter

Before accepting new responsibilities, run through:

  1. Does this require something only I can do?
  2. Is this the highest and best use of my time?
  3. If I say yes to this, what am I saying no to?

If the answers are no, no, and something important — say no.


7. Evidence File

For when imposter syndrome hits. Keep a running file of:

Wins (monthly minimum)

  • Company milestones you led
  • Decisions that worked out well
  • Feedback you received that was genuinely positive

Quotes (capture as they happen)

  • Direct quotes from team members, customers, investors about your impact
  • Emails or messages that reflect trust or appreciation

The hard calls that paid off

  • Decisions you were scared to make that turned out well
  • Times you said no to something that would have hurt the company

When to read it: When you're doubting yourself before a board meeting, a hard conversation, a big pitch. The feeling isn't fact. The evidence file is.