Files
claude-skills-reference/c-level-advisor/culture-architect/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

8.4 KiB
Raw Blame History

name, description, license, metadata
name description license metadata
culture-architect Build, measure, and evolve company culture as operational behavior — not wall posters. Covers mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage. Use when building company values, assessing culture health, designing cultural rituals, creating culture codes, handling culture clashes, or when user mentions culture, values, culture debt, founder culture, or culture code. MIT
version author category domain updated frameworks
1.0.0 Alireza Rezvani c-level culture-leadership 2026-03-05 culture-playbook, culture-code-template

Culture Architect

Culture is what you DO, not what you SAY. This skill builds culture as an operational system — observable behaviors, measurable health, and rituals that scale.

Keywords

culture, company culture, values, mission, vision, culture code, cultural rituals, culture health, values-to-behaviors, founder culture, culture debt, value-washing, culture assessment, culture survey, Netflix culture deck, HubSpot culture code, psychological safety, culture scaling

Core Principle

Culture = (What you reward) + (What you tolerate) + (What you celebrate)

If your values say "transparency" but you punish bearers of bad news — your real value is "optics." Culture is not aspirational. It's descriptive. The work is closing the gap between stated and actual.

Frameworks

1. Mission / Vision / Values Workshop

Run this conversationally, not as a corporate offsite. Three questions:

Mission — Why do we exist (beyond making money)?

  • "What would be lost if we disappeared tomorrow?"
  • Mission is present-tense. "We reduce preventable falls in elderly care." Not "to be the leading..."

Vision — What does winning look like in 510 years?

  • Specific enough to be wrong. "Every care home in Europe uses our system" beats "be the market leader."

Values — What behaviors do we actually model?

  • Start with what you observe, not what sounds good. "What did our last great hire do that nobody asked them to?"
  • Keep to 35. More than 5 and none of them mean anything.

2. Values → Behaviors Translation

This is the work. Every value needs behavioral anchors or it's decoration.

Value Bad version Behavioral anchor
Transparency "We're open and honest" "We share bad news within 24 hours, including to our manager"
Ownership "We take responsibility" "We don't hand off problems — we own them until resolved, even across team boundaries"
Speed "We move fast" "Decisions under €5K happen at team level, same day, no approval needed"
Quality "We don't cut corners" "We stop the line before shipping something we're not proud of"
Customer-first "Customers are our priority" "Any team member can escalate a customer issue to leadership, bypassing normal channels"

Workshop exercise: Write your value. Then ask "How would a new hire know we actually live this on day 30?" If you can't answer concretely, it's not a value — it's an aspiration.

3. Culture Code Creation

A culture code is a public document that describes how you operate. It should scare off the wrong people and attract the right ones.

Structure:

  1. Who we are (mission + context)
  2. Who thrives here (specific behaviors, not adjectives)
  3. Who doesn't thrive here (honest — this is the useful part)
  4. How we make decisions
  5. How we communicate
  6. How we grow people
  7. What we expect of leaders

See templates/culture-code-template.md for a complete template.

Anti-patterns to avoid:

  • "We're a family" — families don't fire each other for performance
  • Listing only positive traits — the "who doesn't thrive here" section is what makes it credible
  • Making it aspirational instead of descriptive

4. Culture Health Assessment

Run quarterly. 812 questions. Anonymous. See references/culture-playbook.md for survey design.

Core areas to measure:

  1. Psychological safety — "Can I raise a concern without fear?"
  2. Clarity — "Do I know how my work connects to company goals?"
  3. Fairness — "Are decisions made consistently and transparently?"
  4. Growth — "Am I learning and being challenged here?"
  5. Trust in leadership — "Do I believe what leadership tells me?"

Score interpretation:

Score Signal Action
80100% Healthy Maintain, celebrate, document
6579% Warning Identify specific friction — don't over-react
5064% Damaged Urgent leadership attention + specific fixes
< 50% Crisis Culture emergency — all-hands intervention

5. Cultural Rituals by Stage

Rituals are the delivery mechanism for culture. What works at 10 people breaks at 100.

Seed stage (< 15 people)

  • Weekly all-hands (30 min): company update + one win + one learning
  • Monthly retrospective: what's working, what's not — no hierarchy
  • "Default to transparency": share everything unless there's a specific reason not to

Early growth (1550 people)

  • Quarterly culture survey: first formal check-in
  • Recognition ritual: explicit, public, tied to values (not just results)
  • Onboarding buddy program: cultural transmission now requires intentional effort
  • Leadership office hours: founders stay accessible as layers appear

Scaling (50200 people)

  • Culture committee (peer-driven, not HR): 46 people rotating quarterly
  • Values-based performance review: culture fit is measured, not assumed
  • Manager training: culture now lives or dies in team leads
  • Department all-hands + company all-hands separate

Large (200+ people)

  • Culture as strategy: explicit annual culture plan with owner and KPIs
  • Internal NPS for culture ("Would you recommend this company to a friend?")
  • Subculture management: engineering culture ≠ sales culture — both must align to company core

6. Culture Anti-Patterns

Value-washing: Listing values you don't practice. Symptom: employees roll their eyes during values discussions.

  • Fix: Run a values audit. Ask "What did the last person who got promoted demonstrate?" If it doesn't match your values, your real values are different.

Culture debt: Accumulating cultural compromises over time. "We'll address the toxic star performer later." Later compounds.

  • Fix: Act on culture violations faster than you think necessary. One tolerated bad behavior destroys what ten good behaviors build.

Founder culture trap: Culture stays frozen at founding team's personality. New hires assimilate or leave.

  • Fix: Explicitly evolve values as you scale. What worked at 10 people (move fast, ask forgiveness) may be destructive at 100 (we need process).

Culture by osmosis: Assuming culture transmits naturally. It did at 10 people. It doesn't at 50.

  • Fix: Make culture intentional. Document it. Teach it. Measure it. Reward it explicitly.

Culture Integration with C-Suite

When... Culture Architect works with... To...
Hiring surge CHRO Ensure culture fit is measured, not guessed
Org reorg COO + CEO Manage culture disruption from structure change
M&A or partnership CEO + COO Detect and resolve culture clashes early
Performance issues CHRO Separate culture fit from skill deficit
Strategy pivot CEO Update values/behaviors that the pivot makes obsolete
Rapid growth All Scale rituals before culture dilutes

Key Questions a Culture Architect Asks

  • "Can you name the last person we fired for culture reasons? What did they do?"
  • "What behavior got your last promoted employee promoted? Is that in your values?"
  • "What would a new hire observe on day 1 that tells them what's really valued here?"
  • "What do we tolerate that we shouldn't? Who knows and does nothing?"
  • "How does a team lead in Berlin know what the culture is in Madrid?"

Red Flags

  • Values posted on the wall, never referenced in reviews or decisions
  • Star performers protected from cultural standards
  • Leaders who "don't have time" for culture rituals
  • New hires feeling the culture is "different than advertised"
  • No mechanism to raise cultural concerns safely
  • Culture survey results never shared with the team

Detailed References

  • references/culture-playbook.md — Netflix analysis, survey design, ritual examples, M&A playbook
  • templates/culture-code-template.md — Culture code document template