release-planning
Plan, coordinate, and execute software releases across environments. Manage versioning, rollout strategies, rollback procedures, and stakeholder communication for smooth deployments.
What this skill does
# Release Planning ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Release planning ensures coordinated deployment of features to production with minimal risk, clear communication, and established rollback procedures. ## When to Use - Planning major feature releases - Coordinating multi-system deployments - Managing database migrations - Rolling out infrastructure changes - Planning go-live strategies - Coordinating customer communication - Preparing for high-traffic periods ## Quick Start Minimal working example: ```yaml Release Plan: Release: v2.5.0 - Customer Portal Redesign Target Release Date: February 15, 2025 Status: Planning Owner: Product Manager --- ## Executive Summary This release delivers the redesigned customer portal with improved UX, performance, and mobile experience. Includes database optimization and infrastructure scaling. Business Impact: - 25% improvement in user conversion - 40% faster load times - Mobile-first experience - Estimated $500K revenue impact --- ## Release Contents // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Release Checklist](references/release-checklist.md) | Release Checklist | | [Versioning Strategy](references/versioning-strategy.md) | Versioning Strategy | | [Rollout & Monitoring](references/rollout-monitoring.md) | Rollout & Monitoring | ## Best Practices ### ✅ DO - Plan releases with clear timeline and milestones - Communicate early and often with stakeholders - Test thoroughly in staging environment - Use phased rollout to reduce risk - Monitor metrics continuously during rollout - Have clear rollback procedure - Document all changes and decisions - Conduct post-release review - Include support team in planning - Plan releases during lower-traffic periods ### ❌ DON'T - Release without adequate testing - Deploy Friday afternoon - Release without monitoring in place - Skip UAT/acceptance testing - Release all major changes together - Deploy without rollback plan - Surprise customers with breaking changes - Release without support team readiness - Make unreviewed last-minute changes - Ignore performance or error metrics
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.