{"id":"3f91e553-031f-48cd-b1c8-dbc63300d007","shortId":"P3XyaD","kind":"skill","title":"team-rituals","tagline":"Design named, templated team rituals (operating cadence).","description":"# Team Rituals\n\n## Scope\n\n**Covers**\n- Designing a **small set of high-leverage team rituals** that drive alignment, execution, learning, and belonging\n- Turning rituals into an **operating system** (not “more meetings”): named rituals, clear owners, repeatable templates, and explicit outputs\n- Creating “Golden Rituals” that are **Named**, **Templated**, and **Known by every new hire by their first Friday**\n\n**When to use**\n- “Our meetings are chaotic; design a better team cadence.”\n- “Define our team operating system / rituals / ceremonies.”\n- “Create named, templated Golden Rituals and a one-pager for onboarding.”\n- “We need better alignment and decision velocity without adding meeting load.”\n\n**When NOT to use**\n- You need to define team culture code, values, or norms first (use `building-team-culture` — rituals should express decisions you’ve already made about culture)\n- You need to facilitate or improve a single meeting or workshop (use `running-effective-meetings` — this skill designs an end-to-end ritual system, not one meeting)\n- You need to set up product operations cadence or cross-team coordination (use `product-operations`)\n- You need engineering-specific ceremonies like sprint retros, incident reviews, or deploy cadences (use `engineering-culture`)\n- You need to define company values, org design, or strategy from scratch (do that first; rituals should express decisions you’ve made)\n- You need HR/legal policy guidance (this is not compliance or legal advice)\n- You’re trying to use rituals for surveillance or performance policing (this will backfire; redesign for trust and psychological safety)\n\n## Inputs\n\n**Minimum required**\n- Team type + size + composition (functions; cross-functional vs single function)\n- Work mode: remote/hybrid/in-office + time zones\n- What’s currently broken (symptoms) + what you want to improve (outcomes)\n- Existing cadence/rituals (or “none”) and what people hate about them\n- Constraints: meeting time budget, decision-making model, tooling (calendar/docs/chat)\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 inputs are still missing, proceed with clearly labeled assumptions and provide 2–3 options.\n- Do not request secrets. If context is sensitive, ask for redacted/high-level descriptions.\n\n## Outputs (deliverables)\n\nProduce a **Team Rituals Pack** in Markdown (in-chat; or as files if the user requests):\n\n1) **Context snapshot** (team, work mode, constraints, goals)\n2) **Ritual inventory audit** (current rituals + what to keep/change/kill)\n3) **Golden Rituals shortlist** (3–7 named rituals mapped to outcomes)\n4) **Ritual specs + templates** (one spec per Golden Ritual: purpose, cadence, owner, agenda, outputs, anti-patterns)\n5) **Onboarding primer** (“Known by first Friday”: 1-page cheatsheet + where templates live)\n6) **Rollout plan** (pilot, comms, calendar/docs setup, training)\n7) **Governance plan** (review cadence, feedback loop, metrics, retirement/iteration rules)\n8) **Risks / Open questions / Next steps** (always included)\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 + outcome definition (what the rituals are for)\n- **Inputs:** user context; [references/INTAKE.md](references/INTAKE.md).\n- **Actions:** Clarify the top 2–3 outcomes (e.g., alignment, decision speed, execution reliability, learning). Set constraints (time budget, remote/async needs). Define what “good” feels like in 4–6 bullets.\n- **Outputs:** Context snapshot + outcome list + constraints.\n- **Checks:** You can explain the “why” in one sentence (“We’re doing this to ____ without ____.”).\n\n### 2) Audit what exists (keep / change / kill)\n- **Inputs:** current meeting list/cadence; pain points.\n- **Actions:** Build a ritual inventory table. For each ritual: purpose, participants, cadence, outputs, and whether it’s working. Identify duplicates and “status-only” meetings.\n- **Outputs:** Ritual inventory audit with a keep/change/kill recommendation.\n- **Checks:** Every existing ritual has an explicit purpose and output; “kill” items have a replacement or rationale.\n\n### 3) Design rules + time budget (make it a system, not meetings)\n- **Inputs:** outcomes + audit.\n- **Actions:** Define a small set of design rules (named, templated, artifact-first, owner-driven, async-by-default). Establish a weekly meeting time budget and decide what must be synchronous vs async.\n- **Outputs:** Ritual design principles + time budget + naming scheme.\n- **Checks:** Total sync time stays within budget; each ritual has an owner and an artifact output.\n\n### 4) Select 3–7 “Golden Rituals” (the minimal set)\n- **Inputs:** outcomes + principles + constraints.\n- **Actions:** Propose 3–7 Golden Rituals that cover: alignment, decisions, execution, learning, and belonging (as needed). Name them with memorable, team-relevant names.\n- **Outputs:** Golden Rituals shortlist + mapping table (ritual → outcome).\n- **Checks:** Each Golden Ritual earns its slot; no “nice-to-have” meetings.\n\n### 5) Write ritual specs + templates (make them repeatable)\n- **Inputs:** Golden Rituals shortlist; [references/TEMPLATES.md](references/TEMPLATES.md).\n- **Actions:** For each Golden Ritual, produce a spec: purpose, cadence, roles, agenda/format, prep, outputs, follow-ups, and anti-patterns. Create the corresponding agenda/notes template.\n- **Outputs:** One “Ritual Spec” per Golden Ritual + copy/paste templates.\n- **Checks:** Rituals are **Named** and **Templated**; outputs are explicit (decisions, priorities, action list, learnings).\n\n### 6) Make them “Known by first Friday” (onboarding + rollout)\n- **Inputs:** Ritual specs; onboarding constraints.\n- **Actions:** Create a 1-page onboarding primer and a rollout plan: pilot order, comms, calendar creation, where templates live, and how new hires learn the rituals in week 1.\n- **Outputs:** Onboarding primer + rollout plan.\n- **Checks:** A new hire can find the rituals, understand purpose, and run one using templates by their first Friday.\n\n### 7) Governance + quality gate (iterate, don’t accumulate)\n- **Inputs:** full draft pack.\n- **Actions:** Define governance: ritual owners, quarterly review, feedback loop, and retirement rules. Run [references/CHECKLISTS.md](references/CHECKLISTS.md) and score with [references/RUBRIC.md](references/RUBRIC.md). Add **Risks / Open questions / Next steps**.\n- **Outputs:** Final Team Rituals Pack.\n- **Checks:** The pack is minimal, adoptable, and has a way to evolve without ritual sprawl.\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 (fix chaotic cadence):** “We’re a 12-person product+engineering team (remote across PST/EST). Meetings feel random and we keep missing decisions. Design Golden Rituals, write templates, and create a first-Friday onboarding primer.”  \nExpected: a small set of named rituals with templates, mapped to outcomes, plus rollout + governance.\n\n**Example 2 (new manager operating system):** “I’m inheriting a team of 7 ICs with low accountability and unclear priorities. Create a weekly operating cadence with minimal meetings and clear artifact outputs.”  \nExpected: ritual inventory audit + a minimal Golden Rituals set + artifact-first templates.\n\n**Boundary example (scope too broad):** “Fix our company culture.”\nResponse: ask what specifically is broken and at what scope; propose a small team-level ritual system only, or redirect to `building-team-culture` for culture code and norms work first.\n\n**Boundary example (single meeting):** “Help me run a better weekly standup — just give me an agenda template.”\nResponse: redirect to `running-effective-meetings` for a single meeting redesign. Use this skill if you want to design the full team operating cadence (standup is one ritual among several).\n\n**Boundary example (engineering ceremonies):** “Set up our sprint retro, incident review, and deploy cadence for the engineering team.”\nResponse: redirect to `engineering-culture` for engineering-specific ceremonies. This skill designs cross-functional team operating cadence, not engineering-specific process.\n\n## Anti-patterns (common failure modes)\n\n1. **Ritual sprawl** — Adding new meetings without killing old ones. Every new ritual must justify its slot against the time budget. If you cannot retire something, you are adding load, not a system.\n2. **Status-only meetings** — Rituals that exist solely for one-directional status reporting. These should be replaced with async updates (written status docs, dashboards) and sync time reserved for decisions, alignment, or learning.\n3. **No artifact output** — Running a ritual that produces no durable artifact (decision log, commitment list, learning summary). If nothing is written down, the ritual did not happen. Every Golden Ritual must produce an output.\n4. **Cargo-cult adoption** — Copying another company's rituals without adapting to your team's context, size, or work mode. “Google does weekly business reviews” does not mean your 6-person startup needs one.\n5. **Rituals without governance** — Never reviewing whether rituals are still working. Institute a quarterly ritual audit with explicit keep/change/kill decisions and retirement rules.","tags":["team","rituals","lenny","skills","plus","liqiongyu","agent-skills","ai-agents","automation","claude","codex","prompt-engineering"],"capabilities":["skill","source-liqiongyu","skill-team-rituals","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/team-rituals","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,479 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-22T00:56:25.845Z","embedding":null,"createdAt":"2026-04-18T22:17:10.695Z","updatedAt":"2026-04-22T00:56:25.845Z","lastSeenAt":"2026-04-22T00:56:25.845Z","tsv":"'1':370,422,464,801,826,927,1162 '12':934 '2':336,378,482,528,979,1195 '3':319,337,387,391,483,591,665,678,1230 '4':398,504,663,1265 '5':314,320,415,721,1300 '6':428,505,784,1295 '7':392,436,462,666,679,851,990 '8':446 'account':994 'accumul':858 'across':940 'action':478,541,605,676,735,781,798,863 'ad':106,1165,1190 'adapt':1276 'add':883 'adopt':899,1269 'advic':236 'agenda':410,1080 'agenda/format':746 'agenda/notes':759 'align':27,101,486,684,1227 'alreadi':135 'alway':452,918 'among':1111 'anoth':1271 'anti':413,754,1157 'anti-pattern':412,753,1156 'artifact':616,661,1008,1020,1232,1241 'artifact-first':615,1019 'ask':311,347,1033 'assumpt':333 'async':622,638,1215 'async-by-default':621 'audit':381,529,569,604,1013,1315 'backfir':250 'belong':31,689 'better':76,100,1073 'boundari':1023,1065,1113 'broad':1027 'broken':279,1037 'budget':300,495,595,630,644,653,1182 'build':126,542,1055 'building-team-cultur':125,1054 'bullet':506 'busi':1289 'cadenc':10,78,175,198,408,440,552,744,930,1002,1106,1126,1150 'cadence/rituals':288 'calendar':812 'calendar/docs':433 'calendar/docs/chat':306 'cannot':1185 'cargo':1267 'cargo-cult':1266 'ceremoni':85,190,1116,1141 'chang':533 'chaotic':73,929 'chat':362 'cheatsheet':424 'check':513,574,647,708,770,832,894 'clarifi':479 'clear':43,331,1007 'code':119,1060 'comm':432,811 'commit':1244 'common':1159 'compani':207,1030,1272 'complianc':233 'composit':263 'constraint':297,376,493,512,675,797 'context':344,371,475,508,1281 'coordin':180 'copi':1270 'copy/paste':768 'correspond':758 'cover':14,683 'creat':50,86,756,799,956,998 'creation':813 'cross':178,266,1146 'cross-funct':265,1145 'cross-team':177 'cult':1268 'cultur':118,128,138,202,1031,1057,1059,1136 'current':278,382,536 'dashboard':1220 'decid':632 'decis':103,132,221,302,487,685,779,949,1226,1242,1319 'decision-mak':301 'default':624 'defin':79,116,206,498,606,864 'definit':467 'deliver':352 'deploy':197,1125 'descript':350 'design':4,15,74,157,210,592,611,641,950,1101,1144 'direct':1207 'doc':1219 'draft':861 'drive':26 'driven':620 'duplic':560 'durabl':1240 'e.g':485 'earn':712 'effect':153,1087 'end':160,162 'end-to-end':159 'engin':188,201,937,1115,1129,1135,1139,1153 'engineering-cultur':200,1134 'engineering-specif':187,1138,1152 'establish':625 'everi':60,575,1172,1258 'evolv':905 'exampl':925,926,978,1024,1066,1114 'execut':28,489,686 'exist':287,531,576,1202 'expand':457 'expect':963,1010 'explain':516 'explicit':48,580,778,1317 'express':131,220 'facilit':142 'failur':1160 'feedback':441,870 'feel':501,943 'file':365 'final':890 'find':837 'first':65,123,217,420,617,789,849,959,1021,1064 'first-friday':958 'fix':928,1028 'follow':750 'follow-up':749 'friday':66,421,790,850,960 'full':860,1103 'function':264,267,270,1147 'gate':854,910 'give':1077 'goal':377 'golden':51,89,388,405,667,680,701,710,730,738,766,951,1016,1259 'good':500 'googl':1286 'govern':437,852,865,977,1303 'guidanc':229,458 'happen':1257 'hate':294 'help':1069 'high':21 'high-leverag':20 'hire':62,820,835 'hr/legal':227 'ic':991 'identifi':559 'improv':144,285 'in-chat':360 'incid':194,1122 'includ':453,919 'info':309 'inherit':986 'input':257,325,473,535,602,672,729,793,859 'institut':1311 'intak':465 'inventori':380,545,568,1012 'item':585 'iter':855 'justifi':1176 'keep':532,947 'keep/change/kill':386,572,1318 'kill':534,584,1169 'known':58,418,787 'label':332 'learn':29,491,687,783,821,1229,1246 'legal':235 'level':1047 'leverag':22 'like':191,502 'list':511,782,1245 'list/cadence':538 'live':427,816 'load':108,1191 'log':1243 'loop':442,871 'low':993 'm':985 'made':136,224 'make':303,596,726,785 'manag':981 'map':395,704,972 'markdown':359 'mean':1293 'meet':40,71,107,147,154,167,298,537,565,601,628,720,942,1005,1068,1088,1092,1167,1199 'memor':695 'metric':443 'minim':670,898,1004,1015 'minimum':258 'miss':308,328,948 'missing-info':307 'mode':272,375,1161,1285 'model':304 'must':634,1175,1261 'name':5,41,55,87,393,613,645,692,699,773,968 'need':99,114,140,169,186,204,226,497,691,1298 'never':1304 'new':61,819,834,980,1166,1173 'next':450,887,923 'nice':717 'nice-to-hav':716 'none':290 'norm':122,1062 'noth':1249 'old':1170 'onboard':97,416,791,796,803,828,961 'one':94,166,402,520,762,844,1109,1171,1206,1299 'one-direct':1205 'one-pag':93 'open':448,885,921 'oper':9,36,82,174,184,982,1001,1105,1149 'option':338 'order':810 'org':209 'outcom':286,397,466,484,510,603,673,707,974 'output':49,351,411,507,553,566,583,639,662,700,748,761,776,827,889,1009,1233,1264 'owner':44,409,619,658,867 'owner-driven':618 'pack':357,862,893,896 'page':423,802 'pager':95 'pain':539 'particip':551 'pattern':414,755,1158 'peopl':293 'per':404,765 'perform':246 'person':935,1296 'pilot':431,809 'plan':430,438,808,831 'plus':975 'point':540 'polic':247 'polici':228 'prep':747 'primer':417,804,829,962 'principl':642,674 'prioriti':780,997 'proceed':329 'process':1155 'produc':353,740,1238,1262 'product':173,183,936 'product-oper':182 'propos':677,1042 'provid':335 'pst/est':941 'psycholog':255 'purpos':407,550,581,743,841 'qualiti':853,909 'quarter':868,1313 'question':315,449,886,922 'random':944 'rational':590 're':238,523,932 'recommend':573 'redacted/high-level':349 'redesign':251,1093 'redirect':1052,1083,1132 'references/checklists.md':876,877,913,914 'references/intake.md':317,318,476,477 'references/rubric.md':881,882,916,917 'references/templates.md':455,456,733,734 'references/workflow.md':459,460 'relev':698 'reliabl':490 'remot':939 'remote/async':496 'remote/hybrid/in-office':273 'repeat':45,728 'replac':588,1213 'report':1209 'request':341,369 'requir':259,911 'reserv':1224 'respons':1032,1082,1131 'retir':873,1186,1321 'retirement/iteration':444 'retro':193,1121 'review':195,439,869,1123,1290,1305 'risk':447,884,920 'ritual':3,8,12,24,33,42,52,84,90,129,163,218,242,356,379,383,389,394,399,406,470,544,549,567,577,640,655,668,681,702,706,711,723,731,739,763,767,771,794,823,839,866,892,907,952,969,1011,1017,1048,1110,1163,1174,1200,1236,1254,1260,1274,1301,1307,1314 'role':745 'rollout':429,792,807,830,976 'rule':445,593,612,874,1322 'run':152,843,875,1071,1086,1234 'running-effective-meet':151,1085 'safeti':256 'scheme':646 'scope':13,1025,1041 'score':879 'scratch':214 'secret':342 'select':664 'sensit':346 'sentenc':521 'set':18,171,492,609,671,966,1018,1117 'setup':434 'sever':1112 'shortlist':390,703,732 'singl':146,269,1067,1091 'size':262,1282 'skill':156,1096,1143 'skill-team-rituals' 'slot':714,1178 'small':17,608,965,1044 'snapshot':372,509 'sole':1203 'someth':1187 'source-liqiongyu' 'spec':400,403,724,742,764,795 'specif':189,1035,1140,1154 'speed':488 'sprawl':908,1164 'sprint':192,1120 'standup':1075,1107 'startup':1297 'status':563,1197,1208,1218 'status-on':562,1196 'stay':651 'step':451,463,888,924 'still':327,1309 'strategi':212,310 'summari':1247 'surveil':244 'symptom':280 'sync':649,1222 'synchron':636 'system':37,83,164,599,983,1049,1194 'tabl':546,705 'team':2,7,11,23,77,81,117,127,179,260,355,373,697,891,938,988,1046,1056,1104,1130,1148,1279 'team-level':1045 'team-relev':696 'team-ritu':1 'templat':6,46,56,88,401,426,454,614,725,760,769,775,815,846,954,971,1022,1081 'time':274,299,323,494,594,629,643,650,1181,1223 'tool':305 'top':481 'topic-agent-skills' 'topic-ai-agents' 'topic-automation' 'topic-claude' 'topic-codex' 'topic-prompt-engineering' 'topic-refoundai' 'topic-skillpack' 'total':648 'train':435 'tri':239 'trust':253 'turn':32 'type':261 'unclear':996 'understand':840 'up':751 'updat':1216 'use':69,112,124,150,181,199,241,845,912,1094 'user':368,474 'valu':120,208 've':134,223 'veloc':104 'vs':268,637 'want':283,1099 'way':903 'week':627,825,1000,1074,1288 'whether':555,1306 'within':652 'without':105,527,906,1168,1275,1302 'work':271,374,558,1063,1284,1310 'workflow':461 'workshop':149 'write':722,953 'written':1217,1251 'zone':275","prices":[{"id":"faf34079-b091-4606-9558-087420541b0f","listingId":"3f91e553-031f-48cd-b1c8-dbc63300d007","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:17:10.695Z"}],"sources":[{"listingId":"3f91e553-031f-48cd-b1c8-dbc63300d007","source":"github","sourceId":"liqiongyu/lenny_skills_plus/team-rituals","sourceUrl":"https://github.com/liqiongyu/lenny_skills_plus/tree/main/skills/team-rituals","isPrimary":false,"firstSeenAt":"2026-04-18T22:17:10.695Z","lastSeenAt":"2026-04-22T00:56:25.845Z"}],"details":{"listingId":"3f91e553-031f-48cd-b1c8-dbc63300d007","quickStartSnippet":null,"exampleRequest":null,"exampleResponse":null,"schema":null,"openapiUrl":null,"agentsTxtUrl":null,"citations":[],"useCases":[],"bestFor":[],"notFor":[],"kindDetails":{"org":"liqiongyu","slug":"team-rituals","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":"8113fdcb922b7956b741198eb9aadfebb24d3e1c","skill_md_path":"skills/team-rituals/SKILL.md","default_branch":"main","skill_tree_url":"https://github.com/liqiongyu/lenny_skills_plus/tree/main/skills/team-rituals"},"layout":"multi","source":"github","category":"lenny_skills_plus","frontmatter":{"name":"team-rituals","description":"Design named, templated team rituals (operating cadence)."},"skills_sh_url":"https://skills.sh/liqiongyu/lenny_skills_plus/team-rituals"},"updatedAt":"2026-04-22T00:56:25.845Z"}}