retro
Start-Stop-Continue retrospective identifying what to Start doing, Stop doing, and Continue doing. Use for sprint retros, personal reflection, team process reviews, or habit audits.
What this skill does
# Start-Stop-Continue Retrospective Run a focused retrospective identifying what to Start, Stop, and Continue. ## Instructions Analyze the subject (project, period, process) and generate specific, actionable items for each category. Focus on behaviors and practices, not people. ### Output Format **Subject**: What period or topic are we reflecting on? **Timeframe**: What period does this cover? --- ## START *New practices or behaviors to begin* | What to Start | Why | Owner | When | |--------------|-----|-------|------| | [Specific action] | [Benefit expected] | [Who] | [Start date] | | [Specific action] | [Benefit expected] | [Who] | [Start date] | | [Specific action] | [Benefit expected] | [Who] | [Start date] | --- ## STOP *Current practices to eliminate* | What to Stop | Why | Owner | When | |--------------|-----|-------|------| | [Specific thing to stop] | [Problem it causes] | [Who] | [End date] | | [Specific thing to stop] | [Problem it causes] | [Who] | [End date] | | [Specific thing to stop] | [Problem it causes] | [Who] | [End date] | --- ## CONTINUE *Things that are working well* | What to Continue | Why It Works | How to Protect It | |-----------------|--------------|-------------------| | [Working practice] | [Value it provides] | [How to ensure it continues] | | [Working practice] | [Value it provides] | [How to ensure it continues] | | [Working practice] | [Value it provides] | [How to ensure it continues] | --- **Top Priority** The single most impactful change from this retro: > [Action] — because [reason] **Check-in** When will we review if these changes are working? > [Date or trigger] ## Guidelines - Be specific: "Start daily standups" not "communicate more" - Be behavioral: Focus on actions, not attitudes - Balance: Aim for 3-5 items per category - Celebrate Continues: Don't skip this section—recognize what's working - Assign owners: Unowned actions don't happen - One priority: If everything is important, nothing is $ARGUMENTS
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.