team-rituals
refoundai/lenny-skills
Design effective team rituals that drive culture and operational efficiency.
What is team-rituals?
Help teams establish named, templated rituals that become part of organizational culture. Use this when building team practices, improving communication, or creating recurring operational rhythms that new employees learn in their first week.
- Understand the specific behavior or outcome a ritual should drive
- Apply the golden rituals framework: named, templated, known by first Friday
- Design rituals beyond generic meetings to solve real problems
- Plan adoption and teach rituals early to new team members
- Create templates so rituals run consistently without the creator present
- Flag common mistakes like too many rituals, unnamed practices, or late introduction
How to install team-rituals
npx skills add https://github.com/refoundai/lenny-skills --skill team-ritualsHow to use team-rituals
- 1.Clarify what outcome or behavior the ritual should drive
- 2.Choose a specific, memorable name for the ritual
- 3.Define a template or structure anyone can follow
- 4.Plan how new employees will learn the ritual in their first week
- 5.Introduce the ritual and monitor adoption over time
- 6.Refine based on feedback and team needs
Use cases
- Designing a weekly all-hands or team sync with clear purpose and structure
- Creating a brainstorming ritual (e.g., Catalyst sessions) with consistent format
- Establishing a Q&A ritual (e.g., Dory) for knowledge sharing and transparency
- Building a one-on-one or tag-up ritual for manager-report alignment
- Replacing multiple ad-hoc meetings with a small set of golden rituals
- Team leads and managers building team culture
- Founders and executives establishing organizational rhythms
- People operations professionals designing onboarding
- Teams trying to improve communication and alignment
team-rituals FAQ
Great companies have a small list of golden rituals, not dozens. Focus on a few high-impact practices rather than creating meeting overload.
A ritual is named, templated, has a specific purpose beyond 'staying aligned,' and becomes part of team culture. It carries shared expectations and can be referenced by name.
Ideally in their first week. If they don't learn rituals early, they'll develop their own habits that may not align with team culture.
Yes. Templates ensure consistency and quality over time, allowing anyone to run the ritual effectively without the creator being present.
Ask if it's solving a real problem or just another meeting. Consider replacing or enhancing it with a more effective practice, or removing it entirely.
Full instructions (SKILL.md)
Source of truth, from refoundai/lenny-skills.
name: team-rituals description: Help users design effective team rituals. Use when someone is building team culture, creating recurring team practices, trying to improve team communication, or establishing operational rhythms for their organization.
Designing Team Rituals
Help the user design effective team rituals using frameworks and insights from 2 product leaders.
How to Help
When the user asks for help with team rituals:
- Understand the goal - Ask what behavior or outcome they want the ritual to drive
- Apply the golden rituals framework - Ensure rituals are named, templated, and known by every employee's first Friday
- Design for specificity - Help create rituals that go beyond generic meetings to drive specific outcomes
- Plan for adoption - Discuss how the ritual will be introduced and maintained over time
Core Principles
Great companies have a small list of golden rituals
Shishir Mehrotra: "Great companies have a very small list of golden rituals. And there are three rules: they're named, every employee knows them by their first Friday, and they're templated." Rituals are the primary vehicle for culture and operational efficiency.
Rituals are the engine of a great team
Lane Shackleton: "The rituals that I've been writing down are very personal. They're my take on how to do this." Go beyond simple meeting management to create rituals like Catalyst sessions, Dory Q&A, Tag-ups, and Flash Tags that serve specific purposes.
Name your rituals
A named ritual becomes a shared concept that can be referenced and improved. "Let's do a Catalyst" is more powerful than "let's brainstorm" because it carries specific expectations.
Template your rituals
Provide structure so anyone can run the ritual consistently. Templates reduce friction and ensure quality even when the ritual creator isn't present.
Teach rituals early
If a new employee doesn't learn your golden rituals in their first week, they'll develop their own habits that may not align with team culture.
Questions to Help Users
- "What outcome are you trying to drive with this ritual?"
- "What will you call this ritual - what's its name?"
- "Can someone run this ritual with just a template, without you being present?"
- "How will new team members learn this ritual in their first week?"
- "Is this ritual solving a real problem, or is it just another meeting?"
- "What existing rituals could this replace or enhance?"
Common Mistakes to Flag
- Too many rituals - Great companies have a small list of golden rituals, not dozens of meetings
- Unnamed rituals - Without a name, a ritual can't become part of the culture's vocabulary
- No template - Rituals without structure degrade in quality over time
- Late introduction - Rituals learned after someone's first week are much harder to adopt
- Generic meetings disguised as rituals - A ritual should have a specific purpose beyond "staying aligned"
Deep Dive
For all 2 insights from 2 guests, see references/guest-insights.md
Related Skills
- Running Effective Meetings
- Building Team Culture
- Written Communication
- Onboarding New Hires
Related skills
More from refoundai/lenny-skills and the wider catalog.

technical-roadmaps
Structure technical roadmaps using diagnosis, guiding policies, and actions—then write them down.

usability-testing
Conduct effective usability testing to validate concepts and uncover user friction before building.

user-onboarding
Design effective product onboarding that drives activation and long-term retention from the first 30 seconds.

vibe-coding
Build functional software through natural language with AI coding tools—no deep technical skills required.

working-backwards
Apply working backwards methodology to clarify product vision before building.

writing-job-descriptions
Write effective job descriptions by defining 12-month success and identifying candidate spikes.