retrospective-facilitation
Facilitate effective retrospectives to capture lessons learned, celebrate successes, and identify actionable improvements for future iterations.
What this skill does
# Retrospective Facilitation ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Retrospectives are critical ceremonies for team learning and continuous improvement. Effective facilitation creates psychological safety, encourages honest feedback, and drives tangible improvements. ## When to Use - End of sprint (regular cadence) - Major milestone completion - Project closure - After significant events or incidents - Team transitions or staff changes - Technology implementations - Process evaluations ## Quick Start Minimal working example: ```yaml Retrospective Planning: Event: Sprint 23 Retrospective Date: Friday, Jan 17, 2025 Duration: 60 minutes Location: Conference Room B / Zoom Facilitator: Sarah (Scrum Master) Participants: 8 team members Invite: Product Owner (optional) --- Retrospective Goals: 1. Celebrate sprint successes 2. Identify what went well 3. Identify what could improve 4. Commit to specific improvements 5. Build team cohesion Format: "Went Well / Didn't Go Well / Ideas" Tool: Miro board for virtual collaboration Pre-Retrospective Preparation: - Send survey: anonymous feedback (24hrs before) - Gather sprint metrics (velocity, bugs, etc.) - Review sprint goals and outcomes // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Retrospective Planning](references/retrospective-planning.md) | Retrospective Planning | | [Facilitation Techniques](references/facilitation-techniques.md) | Facilitation Techniques | | [Action Item Tracking](references/action-item-tracking.md) | Action Item Tracking | | [Retrospective Templates](references/retrospective-templates.md) | Retrospective Templates | ## Best Practices ### ✅ DO - Hold retrospectives regularly (every sprint) - Create psychological safety upfront - Use varied formats to maintain engagement - Include the whole team - Focus on systems, not individuals - Convert insights to specific action items - Assign clear owners and due dates - Track and celebrate completed actions - Review previous actions at start - Thank people for participation and honesty ### ❌ DON'T - Blame individuals or teams - Let dominant voices control discussion - Create action items without owners - Have retrospectives without follow-up - Ignore difficult feedback - Focus only on what went wrong - Hold retrospectives when people are tired/stressed - Skip closing/celebration - Mix retrospectives with status meetings - Ignore patterns across multiple retrospectives
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.