New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Plan a team offsite that earns its cost

Team Offsite Planner Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Team Offsite Planner Skill cover

Plan a team offsite that earns its cost — the purpose split (connection vs decisions vs planning, weighted deliberately), an agenda that alternates work and air, the logistics runbook, and the follow-through that makes Monday different.…

---
name: team-offsite-planner
description: "Plan a team offsite that earns its cost — the purpose split (connection vs decisions vs planning, weighted deliberately), an agenda that alternates work and air, the logistics runbook, and the follow-through that makes Monday different. Use when asked to plan a team offsite, away day, team retreat, quarterly offsite, design two days for the team, or make this offsite not a waste. Produces the purpose weighting, a full agenda with session designs, facilitation notes, a logistics checklist, and the follow-through plan."
---

# Team Offsite Planner Skill

This skill designs a complete team offsite — from goals to minute-by-minute agenda, including session facilitation guides and a logistics checklist.

## Required Inputs

Ask the user for these if not provided:
- **Team size** (number of people)
- **Duration** (half day / full day / 1.5 days / 2 days)
- **Primary goal** (e.g. Q3 planning / team bonding / strategy alignment / retrospective / all of the above)
- **Location type** (office / external venue / remote-first hybrid)
- **Key topics to cover** (if known)
- **Any constraints** (budget, accessibility, team dynamics to be aware of)

Overview

This skill designs a complete team offsite — from goals to minute-by-minute agenda, including session facilitation guides and a logistics checklist.

Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill team-offsite-planner -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/team-offsite-planner
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/ec71944605b65677150a/team-offsite-planner.zip" -OutFile "$env:TEMP\team-offsite-planner.zip"; Expand-Archive "$env:TEMP\team-offsite-planner.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md5.6 KB
Read the files here
mohitagw15856/f6ca7931 file
SKILL.md
Show the full text153 lines

Team Offsite Planner Skill

This skill designs a complete team offsite — from goals to minute-by-minute agenda, including session facilitation guides and a logistics checklist.

Required Inputs

Ask the user for these if not provided:

  • Team size (number of people)
  • Duration (half day / full day / 1.5 days / 2 days)
  • Primary goal (e.g. Q3 planning / team bonding / strategy alignment / retrospective / all of the above)
  • Location type (office / external venue / remote-first hybrid)
  • Key topics to cover (if known)
  • Any constraints (budget, accessibility, team dynamics to be aware of)
  • Remote attendees? (Yes/No — affects session design significantly)

Output Structure


Team Offsite Plan: [Team Name]

Date: [TBD or as provided] Duration: [X days] Attendees: [X people] Goal: [Primary goal from inputs]


1. Offsite Objectives

State 3–5 clear objectives. Each objective should be answerable at the end of the offsite — the team should be able to say "we achieved this" or "we didn't."

  • By the end of this offsite, we will have [specific outcome].

2. Full Agenda

For each time block, produce:

[Time] — [Session Title] (Duration: X min)

  • Type: [Opening / Working session / Workshop / Decision / Social / Break]
  • Owner: [Who runs this — Facilitator / Specific person / Group]
  • Goal: [What this session produces or achieves]
  • Format: [How it runs — e.g. "Whole group discussion", "4 breakout groups of 3", "Silent async doc read + Q&A"]
  • Output: [What leaves the room — e.g. "Agreed list of H2 priorities", "Updated team norms doc", "Go/No-go decision on X"]

Day 1 Example Structure:

Time Session Duration Type
09:00 Arrival & coffee 30 min Social
09:30 Opening & objectives 20 min Framing
09:50 [Strategic session 1] 90 min Working
11:20 Break 15 min —
11:35 [Workshop or decision] 75 min Workshop
13:00 Lunch 60 min Social
14:00 [Working session 2] 90 min Working
15:30 Break 15 min —
15:45 [Team session / retro] 60 min Team
16:45 Day close — commitments 30 min Close
17:15 Social / dinner Open Social

Adapt timing to duration and goals.


3. Session Facilitation Notes

For each working session, provide:

Session: [Name]

Time needed: [X minutes] Materials: [Post-its, Miro board, printed docs, etc.]

Step-by-step facilitation:

  1. [What the facilitator says/does to open — 2–3 min]
  2. [Core activity — describe in detail]
  3. [How to gather/consolidate output]
  4. [Closing move — decision, vote, or commitment]

If the group gets stuck: [One facilitation technique to unstick — e.g. "Dot voting if no consensus", "Parking lot for off-topic items"]

Watch out for: [Common pitfall for this session type — e.g. "The loudest voices dominating. Use silent individual writing first."]


4. Pre-Offsite Prep Checklist

For the organiser to complete before the offsite:

2 weeks before:

  • Book venue and confirm capacity and AV
  • Send calendar invites with travel info
  • Share pre-read or pre-work doc (if any)
  • Confirm dietary requirements and accessibility needs

1 week before:

  • Send agenda to all attendees
  • Assign session owners and brief them
  • Prepare materials (print, Miro boards, name cards)
  • Confirm remote setup if hybrid

Day before:

  • Test AV and video conferencing setup
  • Prepare room layout
  • Confirm headcount and catering

5. Post-Offsite Actions

Template for the summary document to send within 48 hours:

[Team] Offsite Summary — [Date]

  • Decisions made: [List]
  • Actions and owners: [Table: Action | Owner | Due date]
  • Parking lot items: [Topics deferred for follow-up]
  • Next check-in: [When the team will review offsite commitments]

Quality Checks

  • Objectives are measurable at end of day
  • Sessions alternate between high-energy and reflective
  • No single session runs longer than 90 minutes without a break
  • Remote attendees have equal participation in working sessions
  • Each working session has a stated output
  • Agenda has social/informal time built in

Anti-Patterns

  • Do not fill the entire agenda with structured sessions — unstructured social time is essential for team bonding and must be built in
  • Do not schedule more than 90 minutes of intensive working sessions without a break
  • Do not design an offsite without clearly linking each session to the stated goals — purpose must be explicit
  • Do not neglect logistics — venue, travel, dietary requirements, and accessibility must be confirmed before the agenda is finalised
  • Do not plan without an energy management arc — high-energy collaboration sessions should not appear directly after lunch

Example Trigger Phrases

  • "Plan a 1-day offsite for my team of [size]"
  • "Design a 2-day team retreat for [goal]"
  • "Build an agenda for our Q[N] team planning day"
  • "Help me plan a hybrid offsite for [team size] people"
1---
2name: team-offsite-planner
3description: "Plan a team offsite that earns its cost — the purpose split (connection vs decisions vs planning, weighted deliberately), an agenda that alternates work and air, the logistics runbook, and the follow-through that makes Monday different. Use when asked to plan a team offsite, away day, team retreat, quarterly offsite, design two days for the team, or make this offsite not a waste. Produces the purpose weighting, a full agenda with session designs, facilitation notes, a logistics checklist, and the follow-through plan."
4---
5 
6# Team Offsite Planner Skill
7 
8This skill designs a complete team offsite — from goals to minute-by-minute agenda, including session facilitation guides and a logistics checklist.
9 
10## Required Inputs
11 
12Ask the user for these if not provided:
13- **Team size** (number of people)
14- **Duration** (half day / full day / 1.5 days / 2 days)
15- **Primary goal** (e.g. Q3 planning / team bonding / strategy alignment / retrospective / all of the above)
16- **Location type** (office / external venue / remote-first hybrid)
17- **Key topics to cover** (if known)
18- **Any constraints** (budget, accessibility, team dynamics to be aware of)
19- **Remote attendees?** (Yes/No — affects session design significantly)
20 
21## Output Structure
22 
23---
24 
25# Team Offsite Plan: [Team Name]
26**Date:** [TBD or as provided]
27**Duration:** [X days]
28**Attendees:** [X people]
29**Goal:** [Primary goal from inputs]
30 
31---
32 
33## 1. Offsite Objectives
34 
35State 3–5 clear objectives. Each objective should be answerable at the end of the offsite — the team should be able to say "we achieved this" or "we didn't."
36 
37- By the end of this offsite, we will have [specific outcome].
38 
39---
40 
41## 2. Full Agenda
42 
43For each time block, produce:
44 
45**[Time] — [Session Title]** *(Duration: X min)*
46- **Type:** [Opening / Working session / Workshop / Decision / Social / Break]
47- **Owner:** [Who runs this — Facilitator / Specific person / Group]
48- **Goal:** [What this session produces or achieves]
49- **Format:** [How it runs — e.g. "Whole group discussion", "4 breakout groups of 3", "Silent async doc read + Q&A"]
50- **Output:** [What leaves the room — e.g. "Agreed list of H2 priorities", "Updated team norms doc", "Go/No-go decision on X"]
51 
52---
53 
54**Day 1 Example Structure:**
55 
56| Time | Session | Duration | Type |
57|---|---|---|---|
58| 09:00 | Arrival & coffee | 30 min | Social |
59| 09:30 | Opening & objectives | 20 min | Framing |
60| 09:50 | [Strategic session 1] | 90 min | Working |
61| 11:20 | Break | 15 min | — |
62| 11:35 | [Workshop or decision] | 75 min | Workshop |
63| 13:00 | Lunch | 60 min | Social |
64| 14:00 | [Working session 2] | 90 min | Working |
65| 15:30 | Break | 15 min | — |
66| 15:45 | [Team session / retro] | 60 min | Team |
67| 16:45 | Day close — commitments | 30 min | Close |
68| 17:15 | Social / dinner | Open | Social |
69 
70Adapt timing to duration and goals.
71 
72---
73 
74## 3. Session Facilitation Notes
75 
76For each working session, provide:
77 
78### Session: [Name]
79 
80**Time needed:** [X minutes]
81**Materials:** [Post-its, Miro board, printed docs, etc.]
82 
83**Step-by-step facilitation:**
841. [What the facilitator says/does to open — 2–3 min]
852. [Core activity — describe in detail]
863. [How to gather/consolidate output]
874. [Closing move — decision, vote, or commitment]
88 
89**If the group gets stuck:** [One facilitation technique to unstick — e.g. "Dot voting if no consensus", "Parking lot for off-topic items"]
90 
91**Watch out for:** [Common pitfall for this session type — e.g. "The loudest voices dominating. Use silent individual writing first."]
92 
93---
94 
95## 4. Pre-Offsite Prep Checklist
96 
97For the organiser to complete before the offsite:
98 
99**2 weeks before:**
100- [ ] Book venue and confirm capacity and AV
101- [ ] Send calendar invites with travel info
102- [ ] Share pre-read or pre-work doc (if any)
103- [ ] Confirm dietary requirements and accessibility needs
104 
105**1 week before:**
106- [ ] Send agenda to all attendees
107- [ ] Assign session owners and brief them
108- [ ] Prepare materials (print, Miro boards, name cards)
109- [ ] Confirm remote setup if hybrid
110 
111**Day before:**
112- [ ] Test AV and video conferencing setup
113- [ ] Prepare room layout
114- [ ] Confirm headcount and catering
115 
116---
117 
118## 5. Post-Offsite Actions
119 
120Template for the summary document to send within 48 hours:
121 
122**[Team] Offsite Summary — [Date]**
123- **Decisions made:** [List]
124- **Actions and owners:** [Table: Action | Owner | Due date]
125- **Parking lot items:** [Topics deferred for follow-up]
126- **Next check-in:** [When the team will review offsite commitments]
127 
128---
129 
130## Quality Checks
131 
132- [ ] Objectives are measurable at end of day
133- [ ] Sessions alternate between high-energy and reflective
134- [ ] No single session runs longer than 90 minutes without a break
135- [ ] Remote attendees have equal participation in working sessions
136- [ ] Each working session has a stated output
137- [ ] Agenda has social/informal time built in
138 
139## Anti-Patterns
140 
141- [ ] Do not fill the entire agenda with structured sessions — unstructured social time is essential for team bonding and must be built in
142- [ ] Do not schedule more than 90 minutes of intensive working sessions without a break
143- [ ] Do not design an offsite without clearly linking each session to the stated goals — purpose must be explicit
144- [ ] Do not neglect logistics — venue, travel, dietary requirements, and accessibility must be confirmed before the agenda is finalised
145- [ ] Do not plan without an energy management arc — high-energy collaboration sessions should not appear directly after lunch
146 
147## Example Trigger Phrases
148 
149- "Plan a 1-day offsite for my team of [size]"
150- "Design a 2-day team retreat for [goal]"
151- "Build an agenda for our Q[N] team planning day"
152- "Help me plan a hybrid offsite for [team size] people"
153 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with team-offsite-planner

Team Offsite Planner Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Team Offsite Planner Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Team Offsite Planner Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Team Offsite Planner Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillHand local work to a shared OpenClaw Gateway: startTeam handoffopenclaw/agent-skills · by openclawHand local work to a shared OpenClaw Gateway: start a worktree session there as yourself in one request, seeded with a handoff, and get the session URL back.★ 1.1k GitHub starsMCPStandardized templates for every type of agent-to-agent📋 NEXUS Handoff Templatesmsitarzewski/agency-agents · by msitarzewski> Standardized templates for every type of agent-to-agent handoff in the NEXUS pipeline. Consistent handoffs prevent context loss — the #1…★ 154k GitHub starsMCPThe Agency comprises specialized AI agents across every📑 NEXUS Executive Briefmsitarzewski/agency-agents · by msitarzewskiThe Agency comprises specialized AI agents across every division — engineering, design, marketing, security, GIS, product, testing, and…★ 154k GitHub starsMCPNEXUS-Micro | Duration: Minutes to hours | Agents: 3-8🚨 Runbook: Incident Responsemsitarzewski/agency-agents · by msitarzewski> Mode: NEXUS-Micro | Duration: Minutes to hours | Agents: 3-8★ 154k GitHub starsSkillCreate API handoff documentation for frontend developersBackend to frontend handoff docsdavila7/claude-code-templates · by davila7Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.★ 32.3k GitHub starsSkillCreates comprehensive handoff documents for seamless AISession handoffdavila7/claude-code-templates · by davila7Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.★ 32.3k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars