From pm-people
Plan a team offsite from goals to full agenda. Use when asked to plan a team offsite, away day, team retreat, quarterly offsite, or team-building event. Produces a full agenda, session designs, facilitation notes, and logistics checklist.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-people:team-offsite-plannerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill designs a complete team offsite — from goals to minute-by-minute agenda, including session facilitation guides and a logistics checklist.
This skill designs a complete team offsite — from goals to minute-by-minute agenda, including session facilitation guides and a logistics checklist.
Ask the user for these if not provided:
Date: [TBD or as provided] Duration: [X days] Attendees: [X people] Goal: [Primary goal from inputs]
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."
For each time block, produce:
[Time] — [Session Title] (Duration: X min)
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.
For each working session, provide:
Time needed: [X minutes] Materials: [Post-its, Miro board, printed docs, etc.]
Step-by-step facilitation:
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."]
For the organiser to complete before the offsite:
2 weeks before:
1 week before:
Day before:
Template for the summary document to send within 48 hours:
[Team] Offsite Summary — [Date]
npx claudepluginhub mileadev/pm-claude-skills --plugin pm-peopleGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.
2plugins reuse this skill
First indexed Jul 8, 2026