New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Build, measure, and evolve company culture

Culture architect

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

Culture architect cover

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.

---
name: "culture-architect"
description: "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."
license: MIT
metadata:
  version: 1.0.0
  author: Alireza Rezvani
  category: c-level
  domain: culture-leadership
  updated: 2026-03-05
  frameworks: 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

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill culture-architect -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \ | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/c-level-advisor/skills/culture-architect
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/95822beab98fe2ee5780/culture-architect.zip" -OutFile "$env:TEMP\culture-architect.zip"; Expand-Archive "$env:TEMP\culture-architect.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md8.4 KB
  • references/1 file · 12.2 KB
  • templates/1 file · 4.7 KB
Read the files here
alirezarezvani/19392f73 files
SKILL.md
Show the full text168 lines

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 5–10 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 3–5. 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. 8–12 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
80–100% Healthy Maintain, celebrate, document
65–79% Warning Identify specific friction — don't over-react
50–64% 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 (15–50 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 (50–200 people)

  • Culture committee (peer-driven, not HR): 4–6 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
1---
2name: "culture-architect"
3description: "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."
4license: MIT
5metadata:
6 version: 1.0.0
7 author: Alireza Rezvani
8 category: c-level
9 domain: culture-leadership
10 updated: 2026-03-05
11 frameworks: culture-playbook, culture-code-template
12---
13 
14# Culture Architect
15 
16Culture is what you DO, not what you SAY. This skill builds culture as an operational system — observable behaviors, measurable health, and rituals that scale.
17 
18## Keywords
19culture, 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
20 
21## Core Principle
22 
23**Culture = (What you reward) + (What you tolerate) + (What you celebrate)**
24 
25If 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.
26 
27## Frameworks
28 
29### 1. Mission / Vision / Values Workshop
30 
31Run this conversationally, not as a corporate offsite. Three questions:
32 
33**Mission** — Why do we exist (beyond making money)?
34- "What would be lost if we disappeared tomorrow?"
35- Mission is present-tense. "We reduce preventable falls in elderly care." Not "to be the leading..."
36 
37**Vision** — What does winning look like in 5–10 years?
38- Specific enough to be wrong. "Every care home in Europe uses our system" beats "be the market leader."
39 
40**Values** — What behaviors do we actually model?
41- Start with what you observe, not what sounds good. "What did our last great hire do that nobody asked them to?"
42- Keep to 3–5. More than 5 and none of them mean anything.
43 
44### 2. Values → Behaviors Translation
45 
46This is the work. Every value needs behavioral anchors or it's decoration.
47 
48| Value | Bad version | Behavioral anchor |
49|-------|------------|-------------------|
50| Transparency | "We're open and honest" | "We share bad news within 24 hours, including to our manager" |
51| Ownership | "We take responsibility" | "We don't hand off problems — we own them until resolved, even across team boundaries" |
52| Speed | "We move fast" | "Decisions under €5K happen at team level, same day, no approval needed" |
53| Quality | "We don't cut corners" | "We stop the line before shipping something we're not proud of" |
54| Customer-first | "Customers are our priority" | "Any team member can escalate a customer issue to leadership, bypassing normal channels" |
55 
56**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.
57 
58### 3. Culture Code Creation
59 
60A culture code is a public document that describes how you operate. It should scare off the wrong people and attract the right ones.
61 
62**Structure:**
631. Who we are (mission + context)
642. Who thrives here (specific behaviors, not adjectives)
653. Who doesn't thrive here (honest — this is the useful part)
664. How we make decisions
675. How we communicate
686. How we grow people
697. What we expect of leaders
70 
71See `templates/culture-code-template.md` for a complete template.
72 
73**Anti-patterns to avoid:**
74- "We're a family" — families don't fire each other for performance
75- Listing only positive traits — the "who doesn't thrive here" section is what makes it credible
76- Making it aspirational instead of descriptive
77 
78### 4. Culture Health Assessment
79 
80Run quarterly. 8–12 questions. Anonymous. See `references/culture-playbook.md` for survey design.
81 
82**Core areas to measure:**
831. Psychological safety — "Can I raise a concern without fear?"
842. Clarity — "Do I know how my work connects to company goals?"
853. Fairness — "Are decisions made consistently and transparently?"
864. Growth — "Am I learning and being challenged here?"
875. Trust in leadership — "Do I believe what leadership tells me?"
88 
89**Score interpretation:**
90| Score | Signal | Action |
91|-------|--------|--------|
92| 80–100% | Healthy | Maintain, celebrate, document |
93| 65–79% | Warning | Identify specific friction — don't over-react |
94| 50–64% | Damaged | Urgent leadership attention + specific fixes |
95| < 50% | Crisis | Culture emergency — all-hands intervention |
96 
97### 5. Cultural Rituals by Stage
98 
99Rituals are the delivery mechanism for culture. What works at 10 people breaks at 100.
100 
101**Seed stage (< 15 people)**
102- Weekly all-hands (30 min): company update + one win + one learning
103- Monthly retrospective: what's working, what's not — no hierarchy
104- "Default to transparency": share everything unless there's a specific reason not to
105 
106**Early growth (15–50 people)**
107- Quarterly culture survey: first formal check-in
108- Recognition ritual: explicit, public, tied to values (not just results)
109- Onboarding buddy program: cultural transmission now requires intentional effort
110- Leadership office hours: founders stay accessible as layers appear
111 
112**Scaling (50–200 people)**
113- Culture committee (peer-driven, not HR): 4–6 people rotating quarterly
114- Values-based performance review: culture fit is measured, not assumed
115- Manager training: culture now lives or dies in team leads
116- Department all-hands + company all-hands separate
117 
118**Large (200+ people)**
119- Culture as strategy: explicit annual culture plan with owner and KPIs
120- Internal NPS for culture ("Would you recommend this company to a friend?")
121- Subculture management: engineering culture ≠ sales culture — both must align to company core
122 
123### 6. Culture Anti-Patterns
124 
125**Value-washing:** Listing values you don't practice. Symptom: employees roll their eyes during values discussions.
126- 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.
127 
128**Culture debt:** Accumulating cultural compromises over time. "We'll address the toxic star performer later." Later compounds.
129- Fix: Act on culture violations faster than you think necessary. One tolerated bad behavior destroys what ten good behaviors build.
130 
131**Founder culture trap:** Culture stays frozen at founding team's personality. New hires assimilate or leave.
132- Fix: Explicitly evolve values as you scale. What worked at 10 people (move fast, ask forgiveness) may be destructive at 100 (we need process).
133 
134**Culture by osmosis:** Assuming culture transmits naturally. It did at 10 people. It doesn't at 50.
135- Fix: Make culture intentional. Document it. Teach it. Measure it. Reward it explicitly.
136 
137## Culture Integration with C-Suite
138 
139| When... | Culture Architect works with... | To... |
140|---------|---------------------------------|-------|
141| Hiring surge | CHRO | Ensure culture fit is measured, not guessed |
142| Org reorg | COO + CEO | Manage culture disruption from structure change |
143| M&A or partnership | CEO + COO | Detect and resolve culture clashes early |
144| Performance issues | CHRO | Separate culture fit from skill deficit |
145| Strategy pivot | CEO | Update values/behaviors that the pivot makes obsolete |
146| Rapid growth | All | Scale rituals before culture dilutes |
147 
148## Key Questions a Culture Architect Asks
149 
150- "Can you name the last person we fired for culture reasons? What did they do?"
151- "What behavior got your last promoted employee promoted? Is that in your values?"
152- "What would a new hire observe on day 1 that tells them what's really valued here?"
153- "What do we tolerate that we shouldn't? Who knows and does nothing?"
154- "How does a team lead in Berlin know what the culture is in Madrid?"
155 
156## Red Flags
157 
158- Values posted on the wall, never referenced in reviews or decisions
159- Star performers protected from cultural standards
160- Leaders who "don't have time" for culture rituals
161- New hires feeling the culture is "different than advertised"
162- No mechanism to raise cultural concerns safely
163- Culture survey results never shared with the team
164 
165## Detailed References
166- `references/culture-playbook.md` — Netflix analysis, survey design, ritual examples, M&A playbook
167- `templates/culture-code-template.md` — Culture code document template
168 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillExtracting first-party expertise from a subject-matterExpert interviewinhouseseo/superseo-skills · by inhouseseoUse when extracting first-party expertise from a subject-matter expert before writing content. Produces a knowledge document of contrarian takes, specific examples, and surprising outcomes that AI can't fabricate.★ 353 GitHub starsSkillStart of the UGC pipeline for persona researchPersona & ScriptTheMattBerman/scrollclaw · by TheMattBermanStart of the UGC pipeline for persona research, creator profiles, format selection, and scriptwriting. Use when the user is clearly asking for messaging work rather than broad full-pipeline orchestration.★ 71 GitHub starsSkillTell us who you need answers from and what you're missingTo questionnairemattpocock/skills · by mattpocockTell us who you need answers from and what you're missing; get back a clean form you send them to fill in.★ 267k GitHub starsSkillExtracts what the user actually wants instead of what theyInterview meaddyosmani/agent-skills · by addyosmaniExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.★ 98.7k GitHub starsSkillMarketes psychology & mental modelsMarketing Psychology & Mental Modelscoreyhaines31/marketingskills · by coreyhaines31When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.★ 51.1k GitHub stars

More from alirezarezvani

SkillResume a paused experiment/ar:ar-resume — Resume Experimentalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars