Menu

Individual skill

offsite-planner

0upvotes

Plan a team offsite that earns its cost — the purpose split (connection vs. decisions vs. planning, weighted on purpose), the agenda that alternates work and air, the logistics runbook, and the follow-through that makes Monday different from before. Use when asked plan our team offsite, design two days for the team, make this offsite not a waste, or what do we actually do at the offsite. Produces the purpose weighting, the day designs, the logistics checklist, and the commitments-capture that survives re-entry.

skills/offsite-planner/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Offsite Planner Skill

Offsites fail at the extremes: the all-work version (eight hours of conference room that could have been at the office, plus travel) and the all-vibes version (fun had, nothing changed). The honest design starts by *weighting the purposes* — connection, decisions, planning — because they want different formats, and pretending one agenda serves all three equally serves none. Then: sessions designed like workshops (artifacts, not discussions — [workshop-designer](../workshop-designer/SKILL.md) rules), air between them (the corridor conversations are half the value; schedule the corridors), and the follow-through discipline, because an offsite's ROI is measured two weeks later, on Mondays.

## What This Skill Produces

- **The purpose weighting** — connection/decisions/planning split, chosen explicitly with the team's current need
- **The day designs** — session blocks with artifacts, the air between them, the energy arc across days
- **The logistics runbook** — venue, travel, food, the remote-inclusion plan if hybrid, the details that sink offsites when improvised
- **The follow-through kit** — commitments captured with owners/dates, the two-week check, and the "what we decided" note to the wider org

## Required Inputs

Ask for these if not provided:
Back to top