futurist-analyst▌
rysweet/amplihack · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Analyze events through the disciplinary lens of futures studies and strategic foresight, applying established forecasting frameworks (scenario planning, trend analysis, horizon scanning), anticipatory methods, and systems thinking to understand emerging trends, identify drivers of change, envision alternative futures, and develop strategic responses to uncertainty.
Futurist Analyst Skill
Purpose
Analyze events through the disciplinary lens of futures studies and strategic foresight, applying established forecasting frameworks (scenario planning, trend analysis, horizon scanning), anticipatory methods, and systems thinking to understand emerging trends, identify drivers of change, envision alternative futures, and develop strategic responses to uncertainty.
When to Use This Skill
- Strategic Planning: Long-term planning under uncertainty
- Trend Analysis: Identifying emerging patterns and their implications
- Technology Assessment: Evaluating potential impacts of new technologies
- Risk Anticipation: Identifying emerging threats and opportunities
- Scenario Planning: Exploring multiple possible futures
- Innovation Strategy: Understanding future markets and needs
- Policy Development: Forward-looking policy design
- Disruption Analysis: Identifying potential paradigm shifts
Core Philosophy: Futures Thinking
Futures analysis rests on fundamental principles:
The Future is Not Predetermined: Multiple futures are possible. Choices and actions shape which future emerges.
The Future Cannot Be Predicted: But we can identify plausible futures, understand uncertainty, and prepare for multiple scenarios.
Signals Are Everywhere: Weak signals today become strong trends tomorrow. Attending to edges reveals emerging futures.
Systems Thinking Required: Everything connects. Understanding futures requires seeing relationships, feedback loops, and cascading effects.
Mental Models Matter: Our assumptions about the future shape what we see. Challenging assumptions reveals alternative futures.
Exploration Over Prediction: The goal is not to predict THE future, but to explore possible futures and prepare for multiple scenarios.
Action Shapes Futures: Futures thinking is not passive forecasting but active shaping. Understanding possible futures empowers strategic action.
Theoretical Foundations (Expandable)
Framework 1: Three Horizons Framework
Origin: Sharpe, Hodgson, Leicester (International Futures Forum, 2004)
Core Principle: Three overlapping waves of change at different time scales
Three Horizons:
Horizon 1: The Dominant System (Present)
- Current established systems, institutions, practices
- Mature, optimized, but showing signs of decline
- Fit for current context but not emerging challenges
- Time frame: Present to near-term
- Examples: Current business models, incumbent technologies
Horizon 2: Disruptive Innovations (Transition)
- Emerging innovations disrupting H1
- Transitional space between old and new
- Competing paradigms, uncertainty, experimentation
- Some will succeed (become H3), some will fail
- Time frame: Near to medium-term
- Examples: Emerging technologies, new business models, pilot programs
Horizon 3: Future Systems (Emerging)
- Seeds of future systems
- Currently marginal but may become dominant
- Weak signals today, strong trends tomorrow
- Fit for future context we're moving toward
- Time frame: Medium to long-term
- Examples: Radical innovations, paradigm shifts, transformative visions
Key Insights:
- All three horizons coexist at any time
- H1 declines while H2 experiments and H3 emerges
- Transitions are messy, non-linear
- Understanding all three horizons reveals strategic choices
When to Apply: Strategic planning, innovation strategy, understanding systemic change
Sources:
- Sharpe et al., Three Horizons: A Pathways Practice for Transformation (2016)
- Three Horizons - Wikipedia
Framework 2: Scenario Planning
Origin: Herman Kahn (RAND, 1950s), refined by Royal Dutch Shell (1970s)
Core Principle: Develop multiple plausible future scenarios to prepare for uncertainty
Shell Method (Classic Approach):
Step 1: Identify Focal Issue
- What decision, strategy, or question are we addressing?
- What time horizon matters?
Step 2: Identify Driving Forces
- What trends, forces, uncertainties shape the future?
- Categorize: predetermined elements vs. critical uncertainties
Step 3: Select Critical Uncertainties
- What 2-3 uncertainties have highest impact and highest uncertainty?
- These become scenario axes
Step 4: Develop Scenario Logics
- Create 2-4 distinct scenarios based on different combinations of uncertainties
- Each scenario must be internally consistent and plausible
Step 5: Flesh Out Scenarios
- Develop rich narratives for each scenario
- What does this world look like? Feel like?
- What are implications for focal issue?
Step 6: Identify Implications and Options
- What strategies work across scenarios (robust)?
- What early indicators signal which scenario emerging?
- What actions prepare us for each?
Scenario Types:
- Business-as-usual: Continuation of current trends
- Best-case: Optimistic but plausible
- Worst-case: Pessimistic but plausible
- Wildcard: Low probability, high impact
Key Insights:
- Scenarios are not predictions but explorations
- Purpose is to challenge assumptions and expand thinking
- Good scenarios are plausible, divergent, challenging, relevant
- Robust strategies work across multiple scenarios
When to Apply: Strategic planning under high uncertainty, preparing for multiple futures
Sources:
- Peter Schwartz, The Art of the Long View (1991)
- Scenario Planning - Wikipedia
Framework 3: Drivers of Change (STEEP/PESTLE)
Purpose: Systematic framework for identifying forces shaping the future
Five/Six Categories:
Social:
- Demographics (aging, urbanization, migration)
- Values and culture shifts
- Social movements
- Lifestyle changes
- Health and wellness trends
- Education and skills
Technological:
- Emerging technologies (AI, biotech, nanotech, quantum)
- Infrastructure developments
- Digital transformation
- Automation and robotics
- Connectivity and computing power
Economic:
- Growth patterns and cycles
- Globalization vs. fragmentation
- Inequality and wealth distribution
- Labor market shifts
- Resource scarcity or abundance
- Financial system evolution
Environmental:
- Climate change and impacts
- Resource depletion
- Biodiversity loss
- Pollution and ecosystem health
- Renewable energy transition
- Circular economy
Political/Legal:
- Governance models
- Geopolitical shifts
- Regulatory changes
- Power distributions
- Conflict and cooperation
- Institutional strength or weakness
(Optional) Ethical:
- Emerging ethical questions
- Values conflicts
- Moral frameworks
Analysis Approach:
- Scan each category for current trends and emerging shifts
- Assess direction, speed, and magnitude
- Identify interactions between categories
- Determine implications for focal question
Key Insights:
- Changes in one domain affect others (systems thinking)
- Multiple drivers interact to create complex futures
- Some drivers reinforce each other, others conflict
- Comprehensive scanning reduces blind spots
When to Apply: Horizon scanning, trend analysis, understanding context for scenarios
Framework 4: Weak Signals and Wild Cards
Weak Signals:
- Definition: Early indicators of potential change, currently marginal or ambiguous
- Characteristics: Low visibility, fragmented, uncertain significance
- Examples: Niche innovations, edge behaviors, anomalies, surprises
- Value: Detecting weak signals early enables proactive response
Identification Process:
- Scan edges, margins, outsiders (not just mainstream)
- Notice anomalies and surprises
- Track niche innovations
- Listen to fringe voices
- Monitor leading indicators in related domains
Wild Cards:
- Definition: Low probability, high impact events
- Characteristics: Disruptive, paradigm-shifting, often sudden
- Examples: Pandemics, financial crises, breakthrough discoveries, political shocks
- Value: Preparing for wildcards builds resilience
Approach:
- Identify potential wildcards
- Assess probability and impact
- Develop contingency plans
- Build organizational agility
Key Insights:
- Weak signals become strong trends
- Ignoring weak signals leads to strategic surprise
- Wild cards are inevitable even if unpredictable
- Resilience matters more than prediction
When to Apply: Early warning systems, risk anticipation, innovation tracking
Framework 5: Forecasting Methods
Exploratory Forecasting (What could happen?):
- Start from present, project forward
- Identify trends and drivers
- Extrapolate to future possibilities
- Multiple scenarios, not single prediction
Normative Forecasting (What should happen?):
- Start from desired future, work backward
- Define goals and vision
- Identify pathways to achieve
- Also called "backcasting"
Delphi Method:
- Systematic expert consultation
- Multiple rounds to build consensus
- Anonymous to reduce bias
- Iterative refinement of forecasts
Trend Extrapolation:
- Identify historical trends
- Project continuation or inflection
- Assess S-curves (emergence, growth, maturity, decline)
- Caution: Trends can reverse or accelerate
Cross-Impact Analysis:
- How do multiple trends/events interact?
- Reinforcing or dampening effects?
- Cascading consequences
- Network effects
Key Insights:
- Different methods serve different purposes
- Combine methods for robust analysis
- Forecasts are always uncertain—embrace probability ranges
- Update forecasts as new information emerges
When to Apply: Strategic planning, risk assessment, policy development
Core Analytical Frameworks (Expandable)
Framework 1: FUTURES Cone (Voros)
Purpose: Visualize range of possible futures
Structure (expanding cone from present):
Potential Futures: All physically possible futures Plausible Futures: Futures consistent with current knowledge Possible Futures: Futures consistent with current trends and understanding Probable Futures: Futures likely given current trajectory Preferable Futures: Futures we want (normative) Preposterous Futures: Seem impossible now but might not be
Application:
- Map different futures within cone
- Understand which futures are in which category
- Identify preferable futures and pathways toward them
- Challenge assumptions about what's possible
Framework 2: Trend Analysis Framework
Identifying Trends:
- Observe patterns over time
- Distinguish signal from noise
- Assess strength and direction
- Evaluate sustainability
Trend Types:
- Megatrends: Large-scale, long-term, global (e.g., climate change, urbanization)
- Trends: Medium-term, significant (e.g., remote work adoption)
- Fads: Short-term, superficial (e.g., viral products)
S-Curve Pattern:
- Emergence: Slow initial growth
- Growth: Rapid acceleration
- Maturity: Plateau
- Decline: Obsolescence or transformation
Analysis Questions:
- Is this a genuine trend or temporary fluctuation?
- What's driving this trend?
- How far along the S-curve?
- What could accelerate or decelerate?
- What are second-order effects?
Framework 3: Causal Layered Analysis (Sohail Inayatullah)
Purpose: Understand futures at multiple depth levels
Four Layers:
1. Litany (Surface)
- Headlines, trends, issues as commonly understood
- Quantitative data, visible events
- Superficial level
2. Systemic Causes
- Social, political, economic structures
- Institutions, policies, incentives
- How systems produce litany
3. Worldview/Discourse
- Cultural narratives, ideologies
- How we frame and understand issues
- Deeper assumptions
4. Myth/Metaphor (Deepest)
- Archetypal stories and symbols
- Unconscious patterns
- Fundamental narratives shaping reality
Application:
- Analyze issue at all four levels
- Deeper levels reveal alternative futures
- Intervention at different levels has different leverage
Framework 4: Wind Tunneling (Scenario Testing)
Purpose: Test strategies against multiple futures
Process:
- Develop alternative scenarios
- Identify strategic options
- "Wind tunnel" each strategy through each scenario
- Assess performance: Does it succeed? Fail? Need adaptation?
- Identify robust strategies (work across scenarios)
- Identify contingent strategies (work if specific scenario emerges)
- Develop monitoring system to detect which scenario emerging
Outputs:
- Robust strategies (no-regrets moves)
- Hedging strategies (reduce risk)
- Shaping strategies (influence which future emerges)
- Adaptive strategies (flexible response)
Framework 5: Horizon Scanning
Definition: Systematic exploration of emerging issues, trends, and discontinuities
Scanning Domains:
- Technology frontiers
- Social/cultural shifts
- Environmental changes
- Economic developments
- Political/regulatory movements
- Wild card events
Process:
- Define scanning scope and time horizon
- Identify diverse information sources
- Systematically scan for signals
- Collect and categorize findings
- Analyze implications
- Update regularly
Tools:
- Signal tracking databases
- Expert networks
- Crowdsourced scanning
- AI-assisted monitoring
- Workshops and dialogues
Methodological Approaches (Expandable)
Method 1: Scenario Development Workshop
Purpose: Collaborative development of future scenarios
Process:
Phase 1: Prepare (Before workshop)
- Define focal question
- Research trends and drivers
- Identify key uncertainties
Phase 2: Diverge (Day 1)
- Present research
- Brainstorm drivers of change
- Identify critical uncertainties
- Select scenario axes
Phase 3: Develop (Day 1-2)
- Create scenario skeletons
- Develop rich narratives
- Test for plausibility and consistency
- Name scenarios memorably
Phase 4: Explore (Day 2)
- Immerse in each scenario
- Identify implications
- Test strategies
- Identify early indicators
Phase 5: Apply (After workshop)
- Develop monitoring system
- Adapt strategies
- Communicate scenarios widely
- Update periodically
Method 2: Backcasting
Definition: Working backward from desired future to present
Steps:
- Envision: Describe desirable future in detail
- Analyze: What's different from present?
- Backcast: What milestones lead from present to vision?
- Identify: What actions are needed now and next?
- Plan: Develop roadmap and priorities
Comparison to Forecasting:
- Forecasting: Present → Probable Future
- Backcasting: Desired Future → Present Pathway
When to Use: Transformative goals (sustainability, social change), long-term planning
Method 3: Delphi Method
Purpose: Build expert consensus on future developments
Process:
- Round 1: Experts independently forecast
- Round 2: Share aggregate results, experts revise
- Round 3: Further convergence or identify persistent disagreements
- Output: Consensus forecast or range of expert views
Strengths:
- Harnesses expert knowledge
- Anonymous reduces groupthink
- Iterative refinement
Limitations:
- Experts can be wrong
- Groupthink still possible
- Slow process
Method 4: Cross-Impact Analysis
Purpose: Understand how trends and events affect each other
Matrix Approach:
- List key trends/events
- Create matrix: Each trend/event × each trend/event
- Assess: If A occurs, how does it affect B?
- Identify reinforcing loops, dampening effects, cascades
Example:
- Trend A: AI advances
- Trend B: Job automation
- Cross-impact: AI advances accelerate job automation (reinforcing)
- Trend C: Universal basic income adoption
- Cross-impact: Job automation increases political support for UBI
Value: Reveals system dynamics and second-order effects
Method 5: Pre-Mortem Analysis
Purpose: Anticipate failure modes of strategies
Process:
- Imagine strategy has failed catastrophically
- Work backward: Why did it fail?
- Brainstorm all possible failure causes
- Assess likelihood and severity
- Develop mitigation strategies
Value: Surface hidden risks, challenge optimism bias, improve planning
Analysis Rubric
What to Examine
Current State:
- What is the present situation?
- What systems are dominant?
- What are baseline conditions?
Trends and Drivers:
- What forces are shaping change?
- What trends are emerging, maturing, declining?
- What drivers operate across STEEP domains?
Uncertainties:
- What is unpredictable?
- What critical uncertainties have high impact?
- What assumptions might be wrong?
Weak Signals:
- What's emerging at edges?
- What anomalies or surprises?
- What niche innovations?
Alternative Futures:
- What different futures are plausible?
- What are best/worst cases?
- What wildcards could disrupt?
Implications and Strategies:
- What do possible futures mean for stakeholders?
- What strategies are robust across scenarios?
- What early indicators signal which future?
Questions to Ask
Trend Questions:
- What is changing?
- In what direction? How fast?
- What's driving this change?
- How mature is this trend (S-curve position)?
- What could accelerate or reverse?
Uncertainty Questions:
- What is unknowable?
- What could go very differently?
- What assumptions are we making?
- What if we're wrong?
Signal Questions:
- What's emerging at margins?
- What are leading indicators?
- What innovations are taking root?
- What anomalies deserve attention?
System Questions:
- How do elements connect?
- What feedback loops exist?
- What are cascading effects?
- What unintended consequences?
Strategy Questions:
- What futures should we prepare for?
- What strategies work across scenarios?
- What actions shape desired futures?
- What indicators tell us which future is emerging?
Factors to Consider
Time Horizons:
- Near-term (1-3 years)
- Medium-term (3-10 years)
- Long-term (10-30 years)
- Different dynamics at different scales
Uncertainty Levels:
- What we know (facts, established trends)
- What we can estimate (probabilities)
- What's deeply uncertain (multip
How to use futurist-analyst on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add futurist-analyst
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches futurist-analyst from GitHub repository rysweet/amplihack and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate futurist-analyst. Access the skill through slash commands (e.g., /futurist-analyst) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★68 reviews- ★★★★★Ama Okafor· Dec 28, 2024
I recommend futurist-analyst for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Camila Yang· Dec 12, 2024
Registry listing for futurist-analyst matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Soo Kapoor· Dec 8, 2024
Keeps context tight: futurist-analyst is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Anika Taylor· Nov 27, 2024
I recommend futurist-analyst for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Luis Smith· Nov 27, 2024
futurist-analyst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sophia Tandon· Nov 19, 2024
Keeps context tight: futurist-analyst is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Luis Yang· Nov 7, 2024
futurist-analyst fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Sophia Iyer· Nov 3, 2024
futurist-analyst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Luis Robinson· Nov 3, 2024
futurist-analyst reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Luis Martin· Oct 26, 2024
futurist-analyst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 68