offsite-planner
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.
npx skills add mohitagw15856/pm-claude-skills --skill offsite-planner --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 This Skill Produces
- Required Inputs
- Framework: The Design Rules
- Output Format
- The Weighting (told to the team)
- The Days
- Logistics Runbook
- The Two Endings
- Quality Checks
- Anti-Patterns
What does the offsite-planner skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill offsite-planner --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.