running-offsites

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 running-offsites
0 commentsdiscussion
summary

Framework-based guidance for planning and running productive team offsites.

  • Draws on five product leader frameworks covering purpose clarification, team readiness assessment, structure design, and logistics
  • Emphasizes removing teams from day-to-day routines, using physical collaboration tools like whiteboards, and balancing strategy work with social connection
  • Flags common pitfalls including overpacked agendas, soft skills training that masks underlying conflicts, and infrequent in-p
skill.md

Running Offsites

Help the user plan and run effective team offsites using frameworks from 5 product leaders.

How to Help

When the user asks for help with offsites:

  1. Clarify the purpose - Ask what outcome they want from the offsite (strategy, connection, planning)
  2. Assess readiness - Determine if there are underlying team issues that need addressing first
  3. Design the structure - Help them balance work sessions with social connection
  4. Remove friction - Guide them on logistics that make offsites productive

Core Principles

Use "bursts" for remote teams

Brandon Chu: "We've actually instituted with something we call bursts. So bursts at Shopify are the ability for your team generally maybe once a quarter or whatnot, to just come together to do really high velocity creative work together, to hang out together." Remote-first companies should schedule quarterly in-person sessions for high-velocity creative work that's difficult to do asynchronously.

Offsites create space and imprint memory

Claire Hughes Johnson: "When you yank people out of their day-to-day routine, you create space, and also you imprint memory... you're basically activating new parts of their brain, and then you're also having a group experience that cements a belief system usually, or a set of plans." Remove the team from day-to-day routines like email to focus on brainstorming. Use offsites to collaboratively form plans rather than presenting pre-made ones.

Address conflict before soft skills training

Donna Lichaw: "They pulled me aside halfway through the offsite, and they were just like, 'Honestly, storytelling is not going to fix our problems.'" Offsites focused on soft skills may fail if there are underlying interpersonal conflicts. Address team connection and conflict before attempting workshops on influence or communication.

Go laptops-down and use whiteboards

John Mark Nickels: "It was like, laptops down, we're going to spend all day together on a whiteboard. It's like a lost art. People don't use the whiteboards anymore." Deep strategic work requires removing digital distractions. Physical collaboration tools like whiteboards facilitate co-creation and riffing.

Balance social connection with strategy

Megan Cook: "We start off with just doing something fun... And then after that we talk about strategy. We do workshops on different elements of craft boosting that craft together." Start offsites with social activities to build human connection before diving into work. Use semi-annual gatherings to combine strategy alignment with skill-building.

Questions to Help Users

  • "What's the single most important outcome you want from this offsite?"
  • "Are there underlying team conflicts that might undermine the offsite agenda?"
  • "How will you ensure people disconnect from day-to-day work during the offsite?"
  • "What's the right balance between work sessions and social time for this team?"
  • "When did the team last meet in person? What worked well and what didn't?"

Common Mistakes to Flag

  • Packed agendas - Scheduling every minute without leaving space for organic conversation
  • Soft skills over hard problems - Running workshops on communication when the real issue is conflict or strategy
  • Not disconnecting - Allowing email and Slack to compete with offsite activities
  • Too infrequent - Waiting too long between in-person gatherings for remote teams
  • Presenting rather than creating - Using offsites to present pre-made plans instead of collaboratively building them

Deep Dive

For all 5 insights from 5 guests, see references/guest-insights.md

Related Skills

  • running-effective-meetings
  • running-decision-processes
  • post-mortems-retrospectives
how to use running-offsites

How to use running-offsites 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 running-offsites
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 running-offsites

The skills CLI fetches running-offsites 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/running-offsites

Reload or restart Cursor to activate running-offsites. Access the skill through slash commands (e.g., /running-offsites) 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.769 reviews
  • Noor Abebe· Dec 24, 2024

    running-offsites reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Isabella Johnson· Dec 20, 2024

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

  • Daniel Singh· Dec 20, 2024

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

  • Benjamin Verma· Dec 16, 2024

    Registry listing for running-offsites matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Amelia Sethi· Dec 8, 2024

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

  • Pratham Ware· Dec 4, 2024

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

  • Zara Okafor· Nov 27, 2024

    Keeps context tight: running-offsites is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Benjamin Gonzalez· Nov 27, 2024

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

  • Sakshi Patil· Nov 23, 2024

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

  • Alexander Ghosh· Nov 15, 2024

    I recommend running-offsites for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 69

1 / 7