{"id":"af485d37-eaff-41e1-a541-f82e019311da","shortId":"qUGZRD","kind":"skill","title":"building-team-culture","tagline":"Build or refresh a team culture code, norms, and reinforcement plan.","description":"# Building Team Culture\n\n## Scope\n\n**Covers**\n- Diagnosing the *current* culture (strengths, gaps, “sacred cows”, and where psychological safety breaks)\n- Articulating culture as an **operating system** (principles → behaviors → decision rules)\n- Defining **team norms** (communication, meetings, decisions, feedback, conflict)\n- Designing a lightweight **rituals/cadence** map that reinforces the culture\n- Planning rollout + reinforcement (coaching model, hiring/onboarding hooks, measurement)\n\n**When to use**\n- “Create a culture code / values and behaviors for my team.”\n- “Our team norms are unclear—write decision-making + communication norms.”\n- “Psychological safety is low—propose concrete practices and rituals to fix it.”\n- “We’re scaling fast—help us preserve what works and change what doesn’t.”\n- “I’m a new leader—help me listen first and then evolve the culture.”\n\n**When NOT to use**\n- You need to design team meeting cadence, rituals, or operating systems (use `team-rituals` — this skill defines culture principles and norms, not the specific meeting structure)\n- You need engineering-specific practices like code review norms, on-call culture, or incident response culture (use `engineering-culture`)\n- You need a full org restructure, reporting lines, or span-of-control redesign (use `organizational-design`)\n- You need to improve your 1:1 practice or manager-report relationship (use `running-effective-1-1s`)\n- You need an HR/legal investigation, harassment response, or policy/compliance guidance (involve HR/legal)\n- You need to design a full org restructure, comp bands, or performance management system\n- You need to run user/customer research (use `conducting-user-interviews`) or design a full survey instrument (use `designing-surveys`)\n\n## Inputs\n\n**Minimum required**\n- Team context: function, size, seniority mix, reporting line, stage (startup/scale/enterprise)\n- Working model: remote/hybrid/in-office; time zones; any planned org changes\n- Current symptoms with 2–5 examples (e.g., slow decisions, blame, low ownership, stagnation)\n- Desired outcomes: what should be *more true* in 4–12 weeks?\n- Constraints: timeline, leadership support, meeting/time budget, “non-negotiables”\n- Existing artifacts (if any): values, handbook, onboarding, meeting cadences, principles\n- Confidentiality constraints (avoid names/PII; use anonymized examples)\n\n**Missing-info strategy**\n- Ask up to 5 questions from [references/INTAKE.md](references/INTAKE.md) (3–5 at a time).\n- If specifics are missing, proceed with a **default** culture OS and clearly label assumptions.\n- Do not request secrets or personally identifying details; ask for redacted summaries instead.\n\n## Outputs (deliverables)\n\nProduce a **Team Culture Operating System Pack** in Markdown (in-chat; or as files if requested):\n\n1) **Culture snapshot** (what’s true today; strengths/gaps; root causes; “sacred cows”)\n2) **Culture code (v1)** (3–7 principles, each with behaviors, “do/don’t”, decision rules, anti-patterns)\n3) **Team norms** (communication, meetings, decisions, feedback, conflict)\n4) **Rituals & cadence map** (weekly/monthly/quarterly rituals with purpose + owner)\n5) **Rollout + reinforcement plan** (socialization, coaching model, hiring/onboarding hooks)\n6) **Measurement plan** (leading indicators + pulse questions)\n7) **Risks / Open questions / Next steps** (always)\n\nTemplates: [references/TEMPLATES.md](references/TEMPLATES.md)  \nExpanded guidance: [references/WORKFLOW.md](references/WORKFLOW.md)\n\n## Workflow (7 steps)\n\n### 1) Intake + constraints + safety\n- **Inputs:** user context; [references/INTAKE.md](references/INTAKE.md).\n- **Actions:** Confirm goals, constraints, and what *must not* change. Identify whether the request includes HR/legal risk; if yes, pause and recommend HR/legal involvement. Clarify what artifacts the user wants (culture code only vs full pack).\n- **Outputs:** Context snapshot + assumptions/unknowns list.\n- **Checks:** Decision owner and timeline are explicit; sensitive topics are routed appropriately.\n\n### 2) “Listen first”: build a culture snapshot (don’t invent culture yet)\n- **Inputs:** current symptoms; existing artifacts; any examples the user can share.\n- **Actions:** Summarize what the culture rewards/punishes today. Propose a lightweight “listening tour” plan (questions + who to talk to) if the user hasn’t collected input yet.\n- **Outputs:** Draft culture snapshot (strengths, gaps, root causes, tensions, sacred cows).\n- **Checks:** Snapshot is evidence-based (examples), not generic; it distinguishes *stated* vs *lived* culture.\n\n### 3) Diagnose the few moves that matter\n- **Inputs:** culture snapshot.\n- **Actions:** Pick 2–4 priority culture shifts. Identify where “stagnation” exists (lack of visible progress/ambition) and what to change to increase creativity and customer impact. List sacred cows to challenge (and why).\n- **Outputs:** Prioritized culture focus areas + success signals.\n- **Checks:** Each focus area has a leading indicator (observable behaviors within weeks).\n\n### 4) Articulate culture as an operating system (culture code v1)\n- **Inputs:** focus areas; existing values; constraints.\n- **Actions:** Write 3–7 principles. For each: definition, behaviors, do/don’t, decision rules, and anti-patterns. Prefer **articulating what already works** and making gaps explicit.\n- **Outputs:** Culture code (v1) using [references/TEMPLATES.md](references/TEMPLATES.md).\n- **Checks:** Every principle has behavior-level examples; “culture fit” language is replaced with observable standards.\n\n### 5) Turn principles into norms + rituals (make it real)\n- **Inputs:** culture code (v1); team operating reality.\n- **Actions:** Define explicit norms (communication, meetings, decisions, feedback, conflict). Design rituals that reinforce principles (e.g., weekly customer-impact demo, blameless retro, coaching 1:1s). Assign owners and cadences.\n- **Outputs:** Team norms + rituals/cadence map.\n- **Checks:** Rituals have a purpose and an owner; norms reduce ambiguity in common failure modes.\n\n### 6) Reinforcement plan (coaching > policing)\n- **Inputs:** culture code + norms + rituals.\n- **Actions:** Design how the culture will be taught and reinforced: onboarding, hiring signals, promotion expectations, and a lightweight coaching model (peer or craft coaches, not just managers).\n- **Outputs:** Rollout + reinforcement plan (with a 30/60/90-day view).\n- **Checks:** Reinforcement mechanisms exist beyond “announce the doc”; responsibilities are assigned.\n\n### 7) Quality gate + finalize\n- **Inputs:** full draft pack.\n- **Actions:** Run [references/CHECKLISTS.md](references/CHECKLISTS.md) and score with [references/RUBRIC.md](references/RUBRIC.md). Add **Risks / Open questions / Next steps**. Recommend the smallest next experiment (1–2 rituals or norms) to validate impact.\n- **Outputs:** Final Team Culture Operating System Pack.\n- **Checks:** Pack is actionable and internally consistent; tradeoffs and risks are explicit.\n\n## Quality gate (required)\n- Use [references/CHECKLISTS.md](references/CHECKLISTS.md) and [references/RUBRIC.md](references/RUBRIC.md).\n- Always include: **Risks**, **Open questions**, **Next steps**.\n\n## Examples\n\n**Example 1 (new leader, listen-first):** “I’m a new Head of Product joining a remote team of 14. Culture feels low-trust and decisions are slow. Create a culture snapshot, a culture code, and explicit decision-making + meeting norms. Include a 30/60/90 rollout and measurement plan.”  \nExpected: full pack with clear norms and rituals; no generic values.\n\n**Example 2 (scaling + coaching culture):** “We’re growing from 8 → 25. I want to preserve high ownership while adding more coordination. Draft a culture code and a coaching model, plus rituals that keep ambition and creativity high.”  \nExpected: principles + behaviors, coaching model, rituals/cadence map.\n\n**Boundary example (HR/legal):** “We have a harassment complaint and need to ‘fix our culture’ immediately.”\nResponse: direct to HR/legal for investigation and safety; offer to help later with culture articulation, norms, and reinforcement once appropriate.\n\n**Boundary example (redirect to rituals):** “Our meetings are chaotic and we need a better weekly cadence and templates.”\nResponse: redirect to `team-rituals` — this skill defines culture principles and norms, not the specific meeting structure and operating cadence.\n\n**Boundary example (redirect to engineering):** “We need to improve our code review culture and incident response norms for the engineering team.”\nResponse: redirect to `engineering-culture` — this skill covers general team culture, not engineering-specific practices.\n\n## Anti-patterns (common failure modes)\n\n1. **Values as wall art** — Writing aspirational values (“innovation”, “integrity”, “excellence”) without defining observable behaviors, decision rules, or anti-patterns. If a principle cannot be used to make a hard trade-off, it is not actionable.\n2. **Top-down culture decree** — A leader writes the culture code alone and announces it. Culture articulation should start with listening (what’s already true, what’s not) and involve the team in refinement.\n3. **Culture fit as exclusion** — Using “culture fit” to filter out people who are different rather than people who disagree on values. Replace “fit” language with observable behavioral standards that welcome diverse styles.\n4. **All principles, no enforcement** — Defining norms but having no reinforcement mechanism (coaching, feedback, hiring signals, promotion criteria). Culture without consequences is suggestion.\n5. **Ignoring sacred cows** — Avoiding the hard conversations about entrenched behaviors that contradict stated values. The culture snapshot must explicitly name sacred cows and decide whether to challenge or accept them.","tags":["building","team","culture","lenny","skills","plus","liqiongyu","agent-skills","ai-agents","automation","claude","codex"],"capabilities":["skill","source-liqiongyu","skill-building-team-culture","topic-agent-skills","topic-ai-agents","topic-automation","topic-claude","topic-codex","topic-prompt-engineering","topic-refoundai","topic-skillpack"],"categories":["lenny_skills_plus"],"synonyms":[],"warnings":[],"endpointUrl":"https://skills.sh/liqiongyu/lenny_skills_plus/building-team-culture","protocol":"skill","transport":"skills-sh","auth":{"type":"none","details":{"cli":"npx skills add liqiongyu/lenny_skills_plus","source_repo":"https://github.com/liqiongyu/lenny_skills_plus","install_from":"skills.sh"}},"qualityScore":"0.474","qualityRationale":"deterministic score 0.47 from registry signals: · indexed on github topic:agent-skills · 49 github stars · SKILL.md body (9,834 chars)","verified":false,"liveness":"unknown","lastLivenessCheck":null,"agentReviews":{"count":0,"score_avg":null,"cost_usd_avg":null,"success_rate":null,"latency_p50_ms":null,"narrative_summary":null,"summary_updated_at":null},"enrichmentModel":"deterministic:skill-github:v1","enrichmentVersion":1,"enrichedAt":"2026-04-22T06:56:19.085Z","embedding":null,"createdAt":"2026-04-18T22:16:17.547Z","updatedAt":"2026-04-22T06:56:19.085Z","lastSeenAt":"2026-04-22T06:56:19.085Z","tsv":"'-1':222 '1':209,210,221,406,485,786,896,941,1163 '12':315 '14':959 '1s':787 '2':296,418,546,633,897,1002,1201 '25':1011 '3':355,422,435,621,700,1236 '30/60/90':985 '30/60/90-day':855 '4':314,443,634,682,1269 '5':297,350,356,452,747,1292 '6':461,812 '7':423,468,483,701,868 '8':1010 'accept':1321 'action':494,569,631,698,763,822,876,914,1200 'ad':1019 'add':885 'alon':1213 'alreadi':718,1225 'alway':474,932 'ambigu':807 'ambit':1034 'announc':862,1215 'anonym':341 'anti':433,713,1158,1182 'anti-pattern':432,712,1157,1181 'appropri':545,1079 'area':667,673,694 'art':1167 'articul':34,683,716,1074,1218 'artifact':327,519,562 'ask':347,382 'aspir':1169 'assign':788,867 'assumpt':373 'assumptions/unknowns':532 'avoid':338,1296 'band':245 'base':611 'behavior':41,78,427,679,706,736,1040,1177,1263,1302 'behavior-level':735 'better':1093 'beyond':861 'blame':302 'blameless':783 'boundari':1045,1080,1119 'break':33 'budget':322 'build':2,5,16,549 'building-team-cultur':1 'cadenc':143,334,445,791,1095,1118 'call':176 'cannot':1187 'caus':415,602 'challeng':660,1319 'chang':115,292,502,649 'chaotic':1088 'chat':400 'check':534,606,670,731,797,857,911 'clarifi':517 'clear':371,994 'coach':64,457,785,815,840,845,1004,1028,1041,1281 'code':11,75,171,420,524,690,726,758,819,975,1025,1129,1212 'collect':592 'common':809,1160 'communic':47,91,438,767 'comp':244 'complaint':1052 'concret':98 'conduct':258 'conducting-user-interview':257 'confidenti':336 'confirm':495 'conflict':51,442,771 'consequ':1289 'consist':917 'constraint':317,337,487,497,697 'context':275,491,530 'contradict':1304 'control':198 'convers':1299 'coordin':1021 'cover':20,1148 'cow':28,417,605,658,1295,1314 'craft':844 'creat':72,969 'creativ':652,1036 'criteria':1286 'cultur':4,10,18,24,35,60,74,132,155,177,181,185,368,392,407,419,523,551,556,573,597,620,629,636,665,684,689,725,739,757,818,826,907,960,971,974,1005,1024,1058,1073,1107,1131,1145,1151,1205,1211,1217,1237,1242,1287,1308 'current':23,293,559 'custom':654,780 'customer-impact':779 'decid':1316 'decis':42,49,89,301,430,440,535,709,769,966,979,1178 'decision-mak':88,978 'decre':1206 'default':367 'defin':44,154,764,1106,1175,1274 'definit':705 'deliver':388 'demo':782 'design':52,140,203,239,262,269,772,823 'designing-survey':268 'desir':306 'detail':381 'diagnos':21,622 'differ':1250 'direct':1061 'disagre':1255 'distinguish':616 'divers':1267 'do/don':428,707 'doc':864 'doesn':117 'draft':596,874,1022 'e.g':299,777 'effect':220 'enforc':1273 'engin':167,184,1123,1138,1144,1154 'engineering-cultur':183,1143 'engineering-specif':166,1153 'entrench':1301 'everi':732 'evid':610 'evidence-bas':609 'evolv':130 'exampl':298,342,564,612,738,939,940,1001,1046,1081,1120 'excel':1173 'exclus':1240 'exist':326,561,641,695,860 'expand':478 'expect':836,990,1038 'experi':895 'explicit':540,723,765,922,977,1311 'failur':810,1161 'fast':108 'feedback':50,441,770,1282 'feel':961 'file':403 'filter':1245 'final':871,905 'first':127,548,946 'fit':740,1238,1243,1259 'fix':103,1056 'focus':666,672,693 'full':189,241,264,527,873,991 'function':276 'gap':26,600,722 'gate':870,924 'general':1149 'generic':614,999 'goal':496 'grow':1008 'guidanc':233,479 'handbook':331 'harass':229,1051 'hard':1193,1298 'hasn':590 'head':951 'help':109,124,1070 'high':1016,1037 'hire':833,1283 'hiring/onboarding':66,459 'hook':67,460 'hr/legal':227,235,508,515,1047,1063 'identifi':380,503,638 'ignor':1293 'immedi':1059 'impact':655,781,903 'improv':207,1127 'in-chat':398 'incid':179,1133 'includ':507,933,983 'increas':651 'indic':465,677 'info':345 'innov':1171 'input':271,489,558,593,628,692,756,817,872 'instead':386 'instrument':266 'intak':486 'integr':1172 'intern':916 'interview':260 'invent':555 'investig':228,1065 'involv':234,516,1231 'join':954 'keep':1033 'label':372 'lack':642 'languag':741,1260 'later':1071 'lead':464,676 'leader':123,943,1208 'leadership':319 'level':737 'lightweight':54,578,839 'like':170 'line':193,281 'list':533,656 'listen':126,547,579,945,1222 'listen-first':944 'live':619 'low':96,303,963 'low-trust':962 'm':120,948 'make':90,721,753,980,1191 'manag':214,248,848 'manager-report':213 'map':56,446,796,1044 'markdown':397 'matter':627 'measur':68,462,988 'mechan':859,1280 'meet':48,142,162,333,439,768,981,1086,1114 'meeting/time':321 'minimum':272 'miss':344,363 'missing-info':343 'mix':279 'mode':811,1162 'model':65,285,458,841,1029,1042 'move':625 'must':500,1310 'name':1312 'names/pii':339 'need':138,165,187,205,225,237,251,1054,1091,1125 'negoti':325 'new':122,942,950 'next':472,889,894,937 'non':324 'non-negoti':323 'norm':12,46,84,92,158,173,437,751,766,794,805,820,900,982,995,1075,1110,1135,1275 'observ':678,745,1176,1262 'offer':1068 'on-cal':174 'onboard':332,832 'open':470,887,935 'oper':38,146,393,687,761,908,1117 'org':190,242,291 'organiz':202 'organizational-design':201 'os':369 'outcom':307 'output':387,529,595,663,724,792,849,904 'owner':451,536,789,804 'ownership':304,1017 'pack':395,528,875,910,912,992 'pattern':434,714,1159,1183 'paus':512 'peer':842 'peopl':1247,1253 'perform':247 'person':379 'pick':632 'plan':15,61,290,455,463,581,814,852,989 'plus':1030 'polic':816 'policy/compliance':232 'practic':99,169,211,1156 'prefer':715 'preserv':111,1015 'principl':40,156,335,424,702,733,749,776,1039,1108,1186,1271 'priorit':664 'prioriti':635 'proceed':364 'produc':389 'product':953 'progress/ambition':645 'promot':835,1285 'propos':97,576 'psycholog':31,93 'puls':466 'purpos':450,801 'qualiti':869,923 'question':351,467,471,582,888,936 'rather':1251 're':106,1007 'real':755 'realiti':762 'recommend':514,891 'redact':384 'redesign':199 'redirect':1082,1099,1121,1141 'reduc':806 'references/checklists.md':878,879,927,928 'references/intake.md':353,354,492,493 'references/rubric.md':883,884,930,931 'references/templates.md':476,477,729,730 'references/workflow.md':480,481 'refin':1235 'refresh':7 'reinforc':14,58,63,454,775,813,831,851,858,1077,1279 'relationship':216 'remot':956 'remote/hybrid/in-office':286 'replac':743,1258 'report':192,215,280 'request':376,405,506 'requir':273,925 'research':255 'respons':180,230,865,1060,1098,1134,1140 'restructur':191,243 'retro':784 'review':172,1130 'rewards/punishes':574 'risk':469,509,886,920,934 'ritual':101,144,151,444,448,752,773,798,821,898,997,1031,1084,1103 'rituals/cadence':55,795,1043 'rollout':62,453,850,986 'root':414,601 'rout':544 'rule':43,431,710,1179 'run':219,253,877 'running-effect':218 'sacr':27,416,604,657,1294,1313 'safeti':32,94,488,1067 'scale':107,1003 'scope':19 'score':881 'secret':377 'senior':278 'sensit':541 'share':568 'shift':637 'signal':669,834,1284 'size':277 'skill':153,1105,1147 'skill-building-team-culture' 'slow':300,968 'smallest':893 'snapshot':408,531,552,598,607,630,972,1309 'social':456 'source-liqiongyu' 'span':196 'span-of-control':195 'specif':161,168,361,1113,1155 'stage':282 'stagnat':305,640 'standard':746,1264 'start':1220 'startup/scale/enterprise':283 'state':617,1305 'step':473,484,890,938 'strategi':346 'strength':25,599 'strengths/gaps':413 'structur':163,1115 'style':1268 'success':668 'suggest':1291 'summar':570 'summari':385 'support':320 'survey':265,270 'symptom':294,560 'system':39,147,249,394,688,909 'talk':585 'taught':829 'team':3,9,17,45,81,83,141,150,274,391,436,760,793,906,957,1102,1139,1150,1233 'team-ritu':149,1101 'templat':475,1097 'tension':603 'time':287,359 'timelin':318,538 'today':412,575 'top':1203 'top-down':1202 'topic':542 'topic-agent-skills' 'topic-ai-agents' 'topic-automation' 'topic-claude' 'topic-codex' 'topic-prompt-engineering' 'topic-refoundai' 'topic-skillpack' 'tour':580 'trade':1195 'trade-off':1194 'tradeoff':918 'true':312,411,1226 'trust':964 'turn':748 'unclear':86 'us':110 'use':71,136,148,182,200,217,256,267,340,728,926,1189,1241 'user':259,490,521,566,589 'user/customer':254 'v1':421,691,727,759 'valid':902 'valu':76,330,696,1000,1164,1170,1257,1306 'view':856 'visibl':644 'vs':526,618 'wall':1166 'want':522,1013 'week':316,681,778,1094 'weekly/monthly/quarterly':447 'welcom':1266 'whether':504,1317 'within':680 'without':1174,1288 'work':113,284,719 'workflow':482 'write':87,699,1168,1209 'yes':511 'yet':557,594 'zone':288","prices":[{"id":"b36ee50b-8c03-4196-88a4-8c2c0809de01","listingId":"af485d37-eaff-41e1-a541-f82e019311da","amountUsd":"0","unit":"free","nativeCurrency":null,"nativeAmount":null,"chain":null,"payTo":null,"paymentMethod":"skill-free","isPrimary":true,"details":{"org":"liqiongyu","category":"lenny_skills_plus","install_from":"skills.sh"},"createdAt":"2026-04-18T22:16:17.547Z"}],"sources":[{"listingId":"af485d37-eaff-41e1-a541-f82e019311da","source":"github","sourceId":"liqiongyu/lenny_skills_plus/building-team-culture","sourceUrl":"https://github.com/liqiongyu/lenny_skills_plus/tree/main/skills/building-team-culture","isPrimary":false,"firstSeenAt":"2026-04-18T22:16:17.547Z","lastSeenAt":"2026-04-22T06:56:19.085Z"}],"details":{"listingId":"af485d37-eaff-41e1-a541-f82e019311da","quickStartSnippet":null,"exampleRequest":null,"exampleResponse":null,"schema":null,"openapiUrl":null,"agentsTxtUrl":null,"citations":[],"useCases":[],"bestFor":[],"notFor":[],"kindDetails":{"org":"liqiongyu","slug":"building-team-culture","github":{"repo":"liqiongyu/lenny_skills_plus","stars":49,"topics":["agent-skills","ai-agents","automation","claude","codex","prompt-engineering","refoundai","skillpack"],"license":"apache-2.0","html_url":"https://github.com/liqiongyu/lenny_skills_plus","pushed_at":"2026-04-04T06:30:11Z","description":"86 agent-executable skill packs converted from RefoundAI’s Lenny skills (unofficial). Works with Codex + Claude Code.","skill_md_sha":"aba2f4eaa06ceeb63314453d87d1ffecbe673be7","skill_md_path":"skills/building-team-culture/SKILL.md","default_branch":"main","skill_tree_url":"https://github.com/liqiongyu/lenny_skills_plus/tree/main/skills/building-team-culture"},"layout":"multi","source":"github","category":"lenny_skills_plus","frontmatter":{"name":"building-team-culture","description":"Build or refresh a team culture code, norms, and reinforcement plan."},"skills_sh_url":"https://skills.sh/liqiongyu/lenny_skills_plus/building-team-culture"},"updatedAt":"2026-04-22T06:56:19.085Z"}}