Menu
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.
Based on SOC occupation classification
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items. Use when asked to prioritise features, rank a backlog, decide what to build next, or evaluate tradeoffs between competing ideas. Produces a scored, ranked feature list with framework-specific tables, recommended build order, deprioritised items, and assumptions made.
Generate structured developer handoff annotations for a Figma screen or component. Use when asked to write Figma annotations, create dev handoff notes, document a Figma design for developers, or write specs for a screen. Produces a complete annotation set covering interactions, states, spacing, accessibility, and edge cases.
Audit a Figma component library for consistency, coverage gaps, and naming issues. Use when asked to audit components, review a design system, check component consistency, identify missing components, or assess Figma library health. Produces a structured audit report with issues prioritised by impact, naming recommendations, and a fix plan.
Write a structured design brief for a Figma design task from a product requirement or feature request. Use when asked to write a design brief, create a design spec for Figma, turn a PRD into design requirements, or brief a designer on what to build in Figma. Produces a brief with goals, scope, user flows, components needed, constraints, and success criteria.
Runs a PM-perspective design critique focused on product outcomes and user goals, not aesthetics. Use when asked for a PM design critique, a product review of a Figma design, or feedback from a product perspective without needing to be a designer. Produces structured outcome-based feedback tied to user goals, business metrics, and requirement coverage.
Runs a pre-handoff QA checklist on a Figma design before it goes to engineering. Use when asked to QA a Figma design, do a pre-handoff check, or validate a Figma file is ready to build. Produces a structured QA report covering file hygiene, component usage, accessibility, and handoff readiness with explicit pass/fail status per item. Optimised for Opus 4.7 and newer models.
| 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. |
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]
