technical-roadmap-planning
Create comprehensive technical roadmaps aligned with business goals. Plan technology investments, architecture evolution, and infrastructure improvements over quarters and years.
What this skill does
# Technical Roadmap 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 A technical roadmap provides a strategic plan for technology evolution, guiding architectural decisions, infrastructure investments, and capability development aligned with business objectives. ## When to Use - Multi-year technology planning - Architecture modernization initiatives - Platform scaling and reliability improvements - Legacy system migration planning - Infrastructure upgrade scheduling - Technology stack standardization - Innovation investment planning ## Quick Start Minimal working example: ```yaml Technical Roadmap Template: Organization: [Company] Planning Period: 2025-2027 Last Updated: January 2025 Owner: CTO / VP Engineering --- Vision Statement: | Transform our technology platform to enable global scale, improve developer productivity, and deliver world-class customer experiences through modern, cloud-native architecture. Strategic Goals: 1. Reduce infrastructure costs by 40% through cloud optimization 2. Improve deployment frequency from monthly to daily 3. Achieve 99.99% availability (4 nines) 4. Enable data-driven decision making across organization --- ## Q1 2025: Foundation & Planning Theme: Infrastructure Foundation // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Dependency Mapping](references/dependency-mapping.md) | Dependency Mapping | | [Technology Evaluation](references/technology-evaluation.md) | Technology Evaluation | | [Execution Planning](references/execution-planning.md) | Execution Planning | ## Best Practices ### ✅ DO - Align technical roadmap with business strategy - Include time for technical debt reduction - Plan for buffer/contingency in critical paths - Review and update roadmap quarterly - Communicate roadmap transparently - Involve team in planning for buy-in - Prioritize based on business impact - Plan major changes during slower periods - Document rationale for technology choices - Build in learning & experimentation time ### ❌ DON'T - Pursue every new technology trend - Plan at 100% utilization (no buffer) - Ignore team capability and training needs - Make major changes during peak usage - Lock roadmap without flexibility - Underestimate legacy system complexity - Skip security considerations - Plan without resource availability - Ignore risk assessment - Chase technologies without business value
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.