strategic-analysis
Analyze strategic position and recommend plays based on Wardley Mapping. Use for competitive analysis, evolution planning, and strategic decision-making.
What this skill does
# Strategic Analysis Analyze strategic position and recommend plays based on Wardley Mapping principles. ## Workflow ### Step 1: Parse Arguments - **context** (required): The strategic situation to analyze - **perspective** (optional): competitive | evolution | doctrine | comprehensive ### Step 2: Determine Analysis Scope Based on perspective: - **competitive**: Focus on competitive positioning and market plays - **evolution**: Focus on component evolution and movement - **doctrine**: Focus on organizational doctrine and capability - **comprehensive**: All of the above (default) ### Step 3: Research Context Use MCP servers to gather intelligence: 1. Research industry trends and competitive landscape 2. Identify technology evolution patterns 3. Find relevant case studies and precedents ### Step 4: Conduct Analysis #### For Competitive Perspective 1. Invoke `strategy-mapmaker` agent for mapping 2. Invoke `strategic-plays` skill for play identification 3. Analyze competitor positions 4. Identify differentiation opportunities 5. Recommend competitive moves #### For Evolution Perspective 1. Invoke `evolution-analysis` skill 2. Assess current component positions 3. Predict movement trajectories 4. Identify inertia sources 5. Plan evolution strategy #### For Doctrine Perspective 1. Invoke `doctrine-advisor` agent 2. Assess current doctrine maturity 3. Identify capability gaps 4. Recommend doctrine improvements 5. Plan organizational development #### For Comprehensive Execute all three perspectives and synthesize findings. ### Step 5: Synthesize Recommendations Combine findings into: 1. **Situation Assessment**: Where are you now? 2. **Strategic Options**: What can you do? 3. **Recommended Actions**: What should you do? 4. **Risk Analysis**: What could go wrong? 5. **Success Criteria**: How will you measure? ### Step 6: Return Results Present comprehensive strategic analysis with prioritized recommendations. ## Examples ### Buy vs Build Decision ```text /strategic-analysis "buy vs build for authentication" ``` Analyzes the strategic implications of building vs. buying authentication capability. ### Competitive Analysis ```text /strategic-analysis "market entry strategy" perspective="competitive" ``` Focuses on competitive positioning for market entry. ### Technology Evolution ```text /strategic-analysis "container orchestration strategy" perspective="evolution" ``` Analyzes the evolution of container orchestration options. ### Organizational Readiness ```text /strategic-analysis "digital transformation readiness" perspective="doctrine" ``` Assesses organizational doctrine for digital transformation. ## Output Format ```markdown # Strategic Analysis: [Context] ## Executive Summary [Key findings and top recommendations in 3-5 bullets] ## Situation Assessment ### Current Position [Where you are now on the map] ### Competitive Landscape [Who else is here and where are they positioned] ### Evolution State [What's evolving and how fast] ## Analysis by Perspective ### Competitive Analysis [Positioning, threats, opportunities] ### Evolution Analysis [Movement patterns, timing considerations] ### Doctrine Assessment [Organizational capability and gaps] ## Strategic Options | Option | Pros | Cons | Risk | Fit | |--------|------|------|------|-----| | [Option 1] | [Benefits] | [Drawbacks] | [Risk level] | [How well it fits] | ## Recommended Strategy ### Primary Recommendation [What to do and why] ### Supporting Actions 1. [Action 1] 2. [Action 2] 3. [Action 3] ### Timeline - Immediate: [Actions] - Short-term (1-3 months): [Actions] - Medium-term (3-6 months): [Actions] ## Risk Analysis | Risk | Likelihood | Impact | Mitigation | |------|------------|--------|------------| | [Risk] | High/Med/Low | High/Med/Low | [How to address] | ## Success Criteria | Metric | Current | Target | Timeframe | |--------|---------|--------|-----------| | [Metric] | [Now] | [Goal] | [When] | ## Next Steps 1. [Immediate next step] 2. [Following step] 3. [Validation step] ## Assumptions and Limitations - [What was assumed] - [What couldn't be analyzed] ``` ## Analysis Frameworks Used Depending on context, the analysis may incorporate: - **ILC Analysis**: Innovate-Leverage-Commoditize opportunities - **Ecosystem Analysis**: Platform and partner dynamics - **Pioneer-Settler-Town Planner**: Team structure implications - **Inertia Analysis**: Resistance to change factors - **Climatic Patterns**: Industry-wide forces ## Related Commands - `/wardley-map`: Create a Wardley Map first - `/doctrine-assessment`: Deep doctrine assessment ## Related Skills - `strategic-plays`: Strategic gameplay patterns - `evolution-analysis`: Component evolution assessment - `doctrine-assessment`: Organizational doctrine evaluation
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.