Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Temporal Futures Mapping

ASecurity

Explores possible, probable, and preferable futures using scenario thinking. Use when asked about 'scenario planning', 'futures thinking', 'possible futures', 'how might this play out', 'futures cone', or 'what could happen'.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgoapi

Works with

api

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill temporal-futures-mapping --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Temporal Futures Mapping?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Temporal Futures Mapping
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-temporal-futures-mapping/badge)](https://www.skillsdirectory.com/skills/rondoflow-temporal-futures-mapping)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: temporal-futures-mapping
description: "Explores possible, probable, and preferable futures using scenario thinking. Use when asked about 'scenario planning', 'futures thinking', 'possible futures', 'how might this play out', 'futures cone', or 'what could happen'."
---

# Temporal Futures Mapping

The future is not a single path — it is a cone of possibilities that narrows as time passes and choices are made. Scenario thinking does not predict the future; it maps the cone so that plans can be tested against multiple plausible worlds rather than a single assumed one. Plans that only work in one scenario are fragile. Plans robust across several are resilient.

---

## Your Process

**Step 1: Define Time Horizon and Decision Context**
State the specific decision or question being stress-tested and the time horizon (1 year, 5 years, 10 years). The scenarios must be built around a decision, not just as general futures.

**Framing check:** Confirm the specific decision context before continuing. State what you've identified — the actual decision or question being stress-tested and the time horizon — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the decision and time horizon]. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: Identify Key Uncertainties**
Find the 2–3 variables that most shape outcomes but are least predictable. These are the axes along which scenarios diverge. Avoid certainties (they are part of all scenarios) and avoid trivialities (they don't change much).

**Before narrowing:** Show the complete set of candidate uncertainties to the user first. Use `AskUserQuestion`:
- **Question:** "I've identified [N] candidate uncertainties. Before I select the 2–3 most scenario-shaping ones, are there any you'd flag as especially important, or any I've missed?"
- **Header:** "Prioritise"
- **Options:**
  - **Proceed with your selection** — the set looks right
  - **Flag one** — user will name a specific uncertainty to include
  - **Add a missing one** — user will describe it

**Step 3: Build 3–4 Distinct Scenarios**
Span the cone — from possible to plausible to probable to preferable. Each scenario should be:
- Named (a vivid name aids recall)
- Described (the world in this future — what is true, who won, what changed)
- Traceable (the path from now to that world — the sequence of events that produced it)

**Step 4: Test Current Plans**
For each scenario: does the current plan work? Does it fail? Does it create new problems? Plans that are robust across all scenarios are high-confidence. Plans that only work in the most optimistic scenario require hedging.

---

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full analysis** — Complete all steps, reasoning shown throughout
  - **Key findings only** — Bottom-line output, skip step-by-step detail
  - **Most probable future only** — Skip possible and preferable variants, focus on what's likely
  - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

## Output Format

**Key Uncertainties:** [the 2–3 variables driving divergence, with their plausible ranges]

**Scenario Table**

| Name | Description | Path to This World | Implications for Current Plan |
|------|-------------|-------------------|------------------------------|
| | | | |

**Robustness Assessment**
- Robust across all scenarios: [what holds]
- Fragile (only works in one scenario): [what is at risk]
- Hedging required: [where to build optionality]

---

## Notes

Scenarios are not predictions — they are structured hypotheses. The goal is not to determine which will occur but to identify which actions are robust regardless of which occurs.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Futures mapped. What's next?"
- **Header:** "Next"
- **Options:**
  - `/temporal-horizon-mapping` — Set time horizons within the futures map
  - `/decision-premortem-analysis` — Run a premortem on the most likely futures
  - `/probability-scenario-weighting` — Weight the futures by probability
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →