team-rituals

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill team-rituals
0 commentsdiscussion
summary

Design effective team rituals that embed culture and operational rhythms into your organization.

  • Apply the golden rituals framework: name your rituals, template them for consistency, and teach them to every employee by their first week
  • Focus on specificity and purpose—rituals should drive measurable outcomes and solve real problems, not just be generic meetings with new names
  • Plan for adoption and sustainability by ensuring rituals can run without their creator and by introducing the
skill.md

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:

  1. Understand the goal - Ask what behavior or outcome they want the ritual to drive
  2. Apply the golden rituals framework - Ensure rituals are named, templated, and known by every employee's first Friday
  3. Design for specificity - Help create rituals that go beyond generic meetings to drive specific outcomes
  4. 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
how to use team-rituals

How to use team-rituals on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add team-rituals
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill team-rituals

The skills CLI fetches team-rituals from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/team-rituals

Reload or restart Cursor to activate team-rituals. Access the skill through slash commands (e.g., /team-rituals) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.665 reviews
  • Ganesh Mohane· Dec 28, 2024

    Useful defaults in team-rituals — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aditi Agarwal· Dec 24, 2024

    Useful defaults in team-rituals — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Emma Farah· Dec 12, 2024

    team-rituals is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aanya Flores· Dec 8, 2024

    team-rituals has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Aditi Shah· Dec 8, 2024

    We added team-rituals from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Emma Nasser· Nov 27, 2024

    team-rituals fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Harper Sethi· Nov 27, 2024

    Solid pick for teams standardizing on skills: team-rituals is focused, and the summary matches what you get after install.

  • Sakshi Patil· Nov 19, 2024

    team-rituals is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Nikhil Srinivasan· Nov 15, 2024

    team-rituals is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aanya Khan· Nov 3, 2024

    Useful defaults in team-rituals — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 65

1 / 7