explore-migration
Explore migration paths when planning architecture changes. Documents current state, identifies options with trade-offs for informed decision-making.
What this skill does
# Explore Migration Command Explore technical migration options by analyzing current architecture and documenting possible paths with trade-offs. ## Usage ```text /enterprise-architecture:explore-migration <target-state-description> ``` ## Arguments - `target-state-description` (required): Description of the desired end state - Examples: "microservices", "cloud-native", "event-driven", "containerized" ## Examples ```text /enterprise-architecture:explore-migration microservices architecture /enterprise-architecture:explore-migration migrate from monolith to modular monolith /enterprise-architecture:explore-migration replace legacy ORM with modern data access ``` ## Workflow 1. **Analyze Current State** - Scan codebase for architecture patterns - Identify dependencies and coupling - Document current technology stack 2. **Spawn Migration Explorer Agent** Use the `migration-explorer` agent to explore options. The agent: - Documents current state architecture - Identifies multiple migration paths - Analyzes trade-offs for each path - Explores rather than prescribes 3. **Present Migration Options** Display options organized by: - **Current State Summary** - **Migration Options** (with trade-offs) - **Risk Assessment** - **Next Steps for Planning** ## Important Note This command explores technical options. Complete migration planning requires additional business context (budget, team capacity, timeline, compliance needs). The output should inform broader planning discussions, not replace them. ## Output Format ```text ## Migration Exploration: [Target State] ### Scope of This Analysis This document explores technical migration options based on code structure analysis. Complete migration planning requires additional business context: - Budget constraints and approval processes - Team capacity and skill availability - Business timeline requirements - Risk tolerance and compliance needs ### Current State - Architecture pattern: [identified] - Key dependencies: [list] - Technical debt areas: [identified] ### Migration Option 1: [Name] **Approach:** [Description] **Pros:** - [benefit] **Cons:** - [drawback] **Estimated complexity:** [Low/Medium/High] ### Migration Option 2: [Name] [Same structure] ### Migration Option 3: [Name] [Same structure] ### Trade-off Comparison | Factor | Option 1 | Option 2 | Option 3 | | --- | --- | --- | --- | | Complexity | ... | ... | ... | | Risk | ... | ... | ... | | Reversibility | ... | ... | ... | ### Recommended Next Steps 1. [Planning activity] 2. [Validation step] 3. [Stakeholder discussion] ```
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.