c-level-advisor/skills/culture-architect/SKILL.md
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.
npx skillsauth add alirezarezvani/claude-skills culture-architectInstall 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.
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.
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
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.
Run this conversationally, not as a corporate offsite. Three questions:
Mission — Why do we exist (beyond making money)?
Vision — What does winning look like in 5–10 years?
Values — What behaviors do we actually model?
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.
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:
See templates/culture-code-template.md for a complete template.
Anti-patterns to avoid:
Run quarterly. 8–12 questions. Anonymous. See references/culture-playbook.md for survey design.
Core areas to measure:
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 |
Rituals are the delivery mechanism for culture. What works at 10 people breaks at 100.
Seed stage (< 15 people)
Early growth (15–50 people)
Scaling (50–200 people)
Large (200+ people)
Value-washing: Listing values you don't practice. Symptom: employees roll their eyes during values discussions.
Culture debt: Accumulating cultural compromises over time. "We'll address the toxic star performer later." Later compounds.
Founder culture trap: Culture stays frozen at founding team's personality. New hires assimilate or leave.
Culture by osmosis: Assuming culture transmits naturally. It did at 10 people. It doesn't at 50.
| 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 |
references/culture-playbook.md — Netflix analysis, survey design, ritual examples, M&A playbooktemplates/culture-code-template.md — Culture code document templatedevelopment
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.