team-offsite-planner
$
npx mdskill add mohitagw15856/pm-claude-skills/team-offsite-plannerThis skill designs a complete team offsite — from goals to minute-by-minute agenda, including session facilitation guides and a logistics checklist.
SKILL.md
.github/skills/team-offsite-plannerView on GitHub ↗
--- name: team-offsite-planner description: "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." --- # 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 ## 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"
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign 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.
- ab-test-plannerDesign 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.
- accessibility-auditGenerate 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.
- account-planBuild 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.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.