skills/team-offsite-planner/SKILL.md
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.
npx skillsauth add mohitagw15856/pm-claude-skills team-offsite-plannerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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]
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.