plugins/pm-people/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]
development
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners.
development
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
development
Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.
development
Optimize 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.