environmental-scanning-foresight
Monitors external trends across PESTLE dimensions, detects weak signals of emerging change, develops scenario-based futures, and sets adaptive signposts for early warning. Use when scanning external trends for strategic planning, detecting early indicators of change, planning scenarios for multiple futures, setting signposts and indicators for early warning, or when user mentions environmental scanning, horizon scanning, trend analysis, scenario planning, strategic foresight, or futures thinking.
What this skill does
# Environmental Scanning & Foresight
## Table of Contents
- [Workflow](#workflow)
- [Common Patterns](#common-patterns)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)
## Workflow
Copy this checklist and track your progress:
```
Environmental Scanning Progress:
- [ ] Step 1: Define scope and focus areas
- [ ] Step 2: Scan PESTLE forces and trends
- [ ] Step 3: Detect and validate weak signals
- [ ] Step 4: Assess cross-impacts and interactions
- [ ] Step 5: Develop scenarios for plausible futures
- [ ] Step 6: Set signposts and adaptive triggers
```
**Step 1: Define scope and focus areas**
Clarify scanning theme (technology disruption, market evolution, regulatory shift), geographic scope (global, regional, local), time horizon (short 1-2yr, medium 3-5yr, long 5-10yr+), and key uncertainties to explore. See [resources/template.md](resources/template.md#scanning-scope-definition) for scoping framework.
**Step 2: Scan PESTLE forces and trends**
Systematically collect trends across Political, Economic, Social, Technological, Legal, Environmental dimensions. Identify drivers of change (demographics, technology, policy), assess magnitude and direction, and track sources (reports, data, news, expert views). See [resources/template.md](resources/template.md#pestle-scanning-framework) for structured scanning.
**Step 3: Detect and validate weak signals**
Identify early indicators that diverge from mainstream expectations—anomalies, edge cases, emergent behaviors. Validate signal credibility (source quality, supporting evidence, plausibility) and assess potential impact if signal amplifies. See [resources/methodology.md](resources/methodology.md#weak-signal-detection) for detection techniques.
**Step 4: Assess cross-impacts and interactions**
Map how trends interact (reinforcing, offsetting, cascading). Identify critical uncertainties (high impact + high uncertainty) and predetermined elements (high impact + low uncertainty). See [resources/methodology.md](resources/methodology.md#cross-impact-analysis) for interaction mapping.
**Step 5: Develop scenarios for plausible futures**
Create 3-4 distinct, internally consistent scenarios spanning range of outcomes. Build scenarios around critical uncertainties (axes with most impact), develop narrative logic, and test strategies against each scenario. See [resources/template.md](resources/template.md#scenario-development-template) for scenario structure.
**Step 6: Set signposts and adaptive triggers**
Define leading indicators to monitor, set thresholds that trigger strategy adjustment, and establish monitoring cadence (monthly, quarterly, annual). Validate using [resources/evaluators/rubric_environmental_scanning_foresight.json](resources/evaluators/rubric_environmental_scanning_foresight.json). **Minimum standard**: Average score ≥ 3.5.
## Common Patterns
**Pattern 1: Industry Disruption Scanning**
- **Focus**: Technology shifts, business model innovation, competitive dynamics
- **PESTLE emphasis**: Technological (new capabilities), Economic (cost curves), Social (adoption patterns)
- **Weak signals**: Startups with novel approaches, technology breakthroughs in adjacent fields, early adopter behavior
- **Scenarios**: Disruption speed (rapid vs gradual), winning model (incumbent adaptation vs new entrant dominance)
- **Example**: Media industry scanning streaming, AI content generation, attention economy shifts
**Pattern 2: Regulatory & Policy Foresight**
- **Focus**: Government policy, regulatory trends, compliance requirements
- **PESTLE emphasis**: Political (election outcomes, party positions), Legal (regulatory proposals, court decisions)
- **Weak signals**: Pilot programs, stakeholder consultations, legislative drafts in one jurisdiction presaging others
- **Scenarios**: Stringency (light touch vs heavy regulation), speed (gradual vs sudden), scope (sector-specific vs economy-wide)
- **Example**: Finance sector scanning crypto regulation, data privacy laws, central bank digital currencies
**Pattern 3: Market Evolution & Consumer Trends**
- **Focus**: Customer behavior, demand patterns, value shifts
- **PESTLE emphasis**: Social (demographics, values, lifestyle), Economic (income, spending), Technological (enabling platforms)
- **Weak signals**: Subculture behaviors, Gen Z early adoption, influencer/creator economy patterns
- **Scenarios**: Value proposition evolution (what customers prioritize), channel dominance (where they buy), price sensitivity
- **Example**: Retail scanning sustainability values, experiences over ownership, social commerce
**Pattern 4: Geopolitical & Macro Risk Monitoring**
- **Focus**: Political stability, trade relations, conflict risk, economic conditions
- **PESTLE emphasis**: Political (elections, tensions), Economic (growth, inflation, debt), Environmental (climate, resources)
- **Weak signals**: Diplomatic incidents, policy U-turns, capital flows, social unrest indicators
- **Scenarios**: Geopolitical alignment (cooperation vs fragmentation), economic regime (growth vs stagnation), resource availability
- **Example**: Multinational scanning supply chain resilience, tariff risks, energy security
**Pattern 5: Climate & Sustainability Foresight**
- **Focus**: Climate impacts, transition risks, sustainability regulations, stakeholder pressure
- **PESTLE emphasis**: Environmental (physical risks, biodiversity), Political (climate policy), Social (public opinion), Legal (disclosure rules)
- **Weak signals**: Extreme weather anomalies, stranded asset warnings, investor divestment, youth climate activism
- **Scenarios**: Transition speed (orderly vs disorderly), policy stringency (ambitious vs incremental), physical impacts (moderate vs severe)
- **Example**: Energy company scanning net-zero commitments, carbon pricing, renewable cost curves, grid resilience
## Guardrails
**Key requirements:**
1. **Scan systematically across all PESTLE dimensions**: Cover Political, Economic, Social, Technological, Legal, Environmental even if some seem less relevant. Selective scanning creates blind spots, and weak signals often appear in unexpected domains.
2. **Distinguish weak signals from noise**: Weak signals are early indicators with potential impact, not every random anomaly. Validate each signal: Does the source have credibility? Is there supporting evidence? Is amplification plausible? Would the impact be significant if it scales?
3. **Scenarios should be plausible, not preferred or feared**: Scenarios are not predictions or wish fulfillment. They should span the range of outcomes based on critical uncertainties, be internally consistent, and challenge current assumptions. Avoid creating only optimistic scenarios or dystopian extremes.
4. **Focus scenario-building on critical uncertainties**: These have both high impact and high uncertainty. High impact + low uncertainty = predetermined elements (plan for them). High impact + high uncertainty = critical uncertainties (build scenarios around). Low impact = context (note but do not build scenarios around).
5. **Map cross-impacts between trends**: Trends interact: reinforcing trends accelerate (renewable cost decline + climate policy + corporate commitments), offsetting trends create tension (privacy vs personalization), cascading trends trigger others (pandemic to remote work to office demand collapse). Treat trends as interconnected rather than isolated.
6. **Make signposts observable and leading**: Signposts trigger adaptation before the full trend materializes. Leading indicators precede outcomes (building permits before housing prices). Lagging indicators confirm but arrive too late (GDP growth rate). Thresholds should be specific (">20% market share" not "significant adoption") and monitorable (data exists, update frequency known).
7. **Foresight informs strategy without dictating it**: Scenarios reveal possibilities and test strategy robustness, but do not automatically prescribe action. Use 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.