plugins/utopia-quant-pricing/skills/environmental-scanning-foresight/SKILL.md
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.
npx skillsauth add The-Utopia-Studio/skills environmental-scanning-foresightInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 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 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 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 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 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. Minimum standard: Average score ≥ 3.5.
Pattern 1: Industry Disruption Scanning
Pattern 2: Regulatory & Policy Foresight
Pattern 3: Market Evolution & Consumer Trends
Pattern 4: Geopolitical & Macro Risk Monitoring
Pattern 5: Climate & Sustainability Foresight
Key requirements:
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.
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?
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.
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).
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.
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).
Foresight informs strategy without dictating it: Scenarios reveal possibilities and test strategy robustness, but do not automatically prescribe action. Use scenarios to stress-test plans ("does our strategy work in scenarios A, B, C?") and identify no-regrets moves (work in all scenarios) vs hedges (work in some).
Update scans regularly: Environmental conditions change. Set scanning cadence (quarterly PESTLE review, monthly weak signal scan, annual scenario update). Foresight is continuous monitoring, not a one-time exercise.
Common pitfalls:
Key resources:
PESTLE Dimensions:
Time Horizons:
Scenario Archetypes:
Typical workflow time:
When to escalate:
Inputs required:
Outputs produced:
environmental-scanning-foresight.md: PESTLE scan results, weak signals identified, cross-impact analysis, scenarios developed, signposts defined, strategic implicationsdata-ai
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
development
Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
development
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
development
Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.