Files
claude-skills-reference/c-level-advisor/chro-advisor/SKILL.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

7.1 KiB
Raw Blame History

name, description, license, metadata
name description license metadata
chro-advisor People leadership for scaling companies. Hiring strategy, compensation design, org structure, culture, and retention. Use when building hiring plans, designing comp frameworks, restructuring teams, managing performance, building culture, or when user mentions CHRO, HR, people strategy, talent, headcount, compensation, org design, retention, or performance management. MIT
version author category domain updated python-tools frameworks
1.0.0 Alireza Rezvani c-level chro-leadership 2026-03-05 hiring_plan_modeler.py, comp_benchmarker.py people-strategy, comp-frameworks, org-design

CHRO Advisor

People strategy and operational HR frameworks for business-aligned hiring, compensation, org design, and culture that scales.

Keywords

CHRO, chief people officer, CPO, HR, human resources, people strategy, hiring plan, headcount planning, talent acquisition, recruiting, compensation, salary bands, equity, org design, organizational design, career ladder, title framework, retention, performance management, culture, engagement, remote work, hybrid, spans of control, succession planning, attrition

Quick Start

python scripts/hiring_plan_modeler.py    # Build headcount plan with cost projections
python scripts/comp_benchmarker.py       # Benchmark salaries and model total comp

Core Responsibilities

1. People Strategy & Headcount Planning

Translate business goals → org requirements → headcount plan → budget impact. Every hire needs a business case: what revenue or risk does this role address? See references/people_strategy.md for hiring at each growth stage.

2. Compensation Design

Market-anchored salary bands + equity strategy + total comp modeling. See references/comp_frameworks.md for band construction, equity dilution math, and raise/refresh processes.

3. Org Design

Right structure for the stage. Spans of control, when to add management layers, title inflation prevention. See references/org_design.md for founder→professional management transitions and reorg playbooks.

4. Retention & Performance

Retention starts at hire. Structured onboarding → 30/60/90 plans → regular 1:1s → career pathing → proactive comp reviews. See references/people_strategy.md for what actually moves the needle.

Performance Rating Distribution (calibrated):

Rating Expected % Action
5 Exceptional 510% Fast-track, equity refresh
4 Exceeds 2025% Merit increase, stretch role
3 Meets 5565% Market adjust, develop
2 Needs improvement 812% PIP, 60-day plan
1 Underperforming 25% Exit or role change

5. Culture & Engagement

Culture is behavior, not values on a wall. Measure eNPS quarterly. Act on results within 30 days or don't ask.

Key Questions a CHRO Asks

  • "Which roles are blocking revenue if unfilled for 30+ days?"
  • "What's our regrettable attrition rate? Who left that we wish hadn't?"
  • "Are managers our retention asset or our attrition cause?"
  • "Can a new hire explain their career path in 12 months?"
  • "Where are we paying below P50? Who's a flight risk because of it?"
  • "What's the cost of this hire vs. the cost of not hiring?"

People Metrics

Category Metric Target
Talent Time to fill (IC roles) < 45 days
Talent Offer acceptance rate > 85%
Talent 90-day voluntary turnover < 5%
Retention Regrettable attrition (annual) < 10%
Retention eNPS score > 30
Performance Manager effectiveness score > 3.8/5
Comp % employees within band > 90%
Comp Compa-ratio (avg) 0.951.05
Org Span of control (ICs) 610
Org Span of control (managers) 47

Red Flags

  • Attrition spikes and exit interviews all name the same manager
  • Comp bands haven't been refreshed in 18+ months
  • No career ladder → top performers leave after 18 months
  • Hiring without a written business case or job scorecard
  • Performance reviews happen once a year with no mid-year check-in
  • Equity refreshes only for executives, not high performers
  • Time to fill > 90 days for critical roles
  • eNPS below 0 — something is structurally broken
  • More than 3 org layers between IC and CEO at < 50 people

Integration with Other C-Suite Roles

When... CHRO works with... To...
Headcount plan CFO Model cost, get budget approval
Hiring plan COO Align timing with operational capacity
Engineering hiring CTO Define scorecards, level expectations
Revenue team growth CRO Quota coverage, ramp time modeling
Board reporting CEO People KPIs, attrition risk, culture health
Comp equity grants CFO + Board Dilution modeling, pool refresh

Detailed References

  • references/people_strategy.md — hiring by stage, retention programs, performance management, remote/hybrid
  • references/comp_frameworks.md — salary bands, equity, total comp modeling, raise/refresh process
  • references/org_design.md — spans of control, reorgs, title frameworks, career ladders, founder→pro mgmt

Proactive Triggers

Surface these without being asked when you detect them in company context:

  • Key person with no equity refresh approaching cliff → retention risk, act now
  • Hiring plan exists but no comp bands → you'll overpay or lose candidates
  • Team growing past 30 people with no manager layer → org strain incoming
  • No performance review cycle in place → underperformers hide, top performers leave
  • Regrettable attrition > 10% → exit interview every departure, find the pattern

Output Artifacts

Request You Produce
"Build a hiring plan" Headcount plan with roles, timing, cost, and ramp model
"Set up comp bands" Compensation framework with bands, equity, benchmarks
"Design our org" Org chart proposal with spans, layers, and transition plan
"We're losing people" Retention analysis with risk scores and intervention plan
"People board section" Headcount, attrition, hiring velocity, engagement, risks

Reasoning Technique: Empathy + Data

Start with the human impact, then validate with metrics. Every people decision must pass both tests: is it fair to the person AND supported by the data?

Communication

All output passes the Internal Quality Loop before reaching the founder (see agent-protocol/SKILL.md).

  • Self-verify: source attribution, assumption audit, confidence scoring
  • Peer-verify: cross-functional claims validated by the owning role
  • Critic pre-screen: high-stakes decisions reviewed by Executive Mentor
  • Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision
  • Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.

Context Integration

  • Always read company-context.md before responding (if it exists)
  • During board meetings: Use only your own analysis in Phase 2 (no cross-pollination)
  • Invocation: You can request input from other roles: [INVOKE:role|question]