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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfuturist-analystExecute the skills CLI command in your project's root directory to begin installation:
Fetches futurist-analyst from rysweet/amplihack and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate futurist-analyst. Access via /futurist-analyst in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
44
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
44
stars
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.
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.
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)
Horizon 2: Disruptive Innovations (Transition)
Horizon 3: Future Systems (Emerging)
Key Insights:
When to Apply: Strategic planning, innovation strategy, understanding systemic change
Sources:
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
Step 2: Identify Driving Forces
Step 3: Select Critical Uncertainties
Step 4: Develop Scenario Logics
Step 5: Flesh Out Scenarios
Step 6: Identify Implications and Options
Scenario Types:
Key Insights:
When to Apply: Strategic planning under high uncertainty, preparing for multiple futures
Sources:
Purpose: Systematic framework for identifying forces shaping the future
Five/Six Categories:
Social:
Technological:
Economic:
Environmental:
Political/Legal:
(Optional) Ethical:
Analysis Approach:
Key Insights:
When to Apply: Horizon scanning, trend analysis, understanding context for scenarios
Weak Signals:
Identification Process:
Wild Cards:
Approach:
Key Insights:
When to Apply: Early warning systems, risk anticipation, innovation tracking
Exploratory Forecasting (What could happen?):
Normative Forecasting (What should happen?):
Delphi Method:
Trend Extrapolation:
Cross-Impact Analysis:
Key Insights:
When to Apply: Strategic planning, risk assessment, policy development
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:
Identifying Trends:
Trend Types:
S-Curve Pattern:
Analysis Questions:
Purpose: Understand futures at multiple depth levels
Four Layers:
1. Litany (Surface)
2. Systemic Causes
3. Worldview/Discourse
4. Myth/Metaphor (Deepest)
Application:
Purpose: Test strategies against multiple futures
Process:
Outputs:
Definition: Systematic exploration of emerging issues, trends, and discontinuities
Scanning Domains:
Process:
Tools:
Purpose: Collaborative development of future scenarios
Process:
Phase 1: Prepare (Before workshop)
Phase 2: Diverge (Day 1)
Phase 3: Develop (Day 1-2)
Phase 4: Explore (Day 2)
Phase 5: Apply (After workshop)
Definition: Working backward from desired future to present
Steps:
Comparison to Forecasting:
When to Use: Transformative goals (sustainability, social change), long-term planning
Purpose: Build expert consensus on future developments
Process:
Strengths:
Limitations:
Purpose: Understand how trends and events affect each other
Matrix Approach:
Example:
Value: Reveals system dynamics and second-order effects
Purpose: Anticipate failure modes of strategies
Process:
Value: Surface hidden risks, challenge optimism bias, improve planning
Current State:
Trends and Drivers:
Uncertainties:
Weak Signals:
Alternative Futures:
Implications and Strategies:
Trend Questions:
Uncertainty Questions:
Signal Questions:
System Questions:
Strategy Questions:
Time Horizons:
Uncertainty Levels:
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend futurist-analyst for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for futurist-analyst matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: futurist-analyst is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend futurist-analyst for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
futurist-analyst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: futurist-analyst is the kind of skill you can hand to a new teammate without a long onboarding doc.
futurist-analyst fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
futurist-analyst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
futurist-analyst reduced setup friction for our internal harness; good balance of opinion and flexibility.
futurist-analyst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 68