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 Horizon Mapping

ASecurity

Maps consequences of a decision across short, medium, and long time horizons. Use when asked about 'time horizons', 'what does this look like in 5 years', 'short-term vs long-term', 'map the implications over time', or 'think through the long-term'.

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

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Temporal Horizon Mapping?

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

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

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

Download with Pro
Files
SKILL.md
---
name: temporal-horizon-mapping
description: "Maps consequences of a decision across short, medium, and long time horizons. Use when asked about 'time horizons', 'what does this look like in 5 years', 'short-term vs long-term', 'map the implications over time', or 'think through the long-term'."
---

# Temporal Horizon Mapping

Decisions that look good now often look very different at 1, 3, or 10 years. The most consequential errors in judgment come not from bad reasoning in the moment but from evaluating a decision at the wrong time horizon — optimizing for the immediate while the real costs land later. Making all three horizons explicit forces the tradeoff into view rather than leaving it implicit.

---

## Your Process

**Step 1: State the Decision**
Name the decision being evaluated and the current context in which it is being made. Clarity here prevents analysis drifting to adjacent decisions.

**Framing check:** Confirm the specific decision before continuing. State what you've identified — the actual decision being evaluated and the context in which it is being made — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the specific decision and its context]. 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: Map Immediate Consequences (0–3 months)**
What is the likely state immediately after acting? What resources are committed or freed? Who is affected and how? What has this enabled or closed off in the near term?

**Step 3: Map Medium-Term Consequences (6–24 months)**
What does the situation look like after the initial effects have compounded? What second-order effects emerge? Who gains or loses standing? What dependencies or path-dependencies have formed?

**Step 4: Map Long-Term Consequences (3+ years)**
What has the decision made likely or unlikely at scale and over time? What is the structural change — to capabilities, relationships, markets, culture? What would be very difficult to reverse by this point?

**Step 5: Flag Reversals**
Identify decisions that look positive short-term but create long-term problems — and the reverse. These reversals are the highest-value output of this analysis.

**Step 6: Identify the Governing Horizon**
**Before narrowing:** Show the consequences mapped across all three horizons to the user first. Use `AskUserQuestion`:
- **Question:** "I've mapped consequences across all three horizons. Before I identify the governing horizon, are there any consequences you'd flag as especially significant, or any I've missed?"
- **Header:** "Prioritise"
- **Options:**
  - **Proceed with your selection** — the mapped consequences look right
  - **Flag one** — user will name a specific consequence to weight more heavily
  - **Add a missing one** — user will describe a consequence not yet captured

At which horizon do the most significant consequences actually land? Is that the horizon currently being used to evaluate this decision? Mismatched horizons are the primary source of poor long-term decisions made in good faith.

---

## 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
  - **Long-term consequences only** — What emerges beyond the obvious timeframe, skip near-term
  - **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

**Horizon Table**

| Horizon | Timeframe | Likely State | Enabled / Foreclosed | Who Is Better / Worse Off |
|---------|----------|-------------|---------------------|--------------------------|
| Immediate | 0–3 months | | | |
| Medium | 6–24 months | | | |
| Long | 3+ years | | | |

**Reversal Flags:** [decisions that look good short-term but create long-term problems, or vice versa]

**Governing Horizon:** [which horizon should drive this decision + why it differs from current evaluation horizon if applicable]

---

## Notes

Short-term and long-term are not automatically in conflict — some decisions improve all horizons. Identify those as high-confidence choices; the real analysis is needed where horizons diverge.

---

## What's Next

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

- **Question:** "Horizons mapped. What's next?"
- **Header:** "Next"
- **Options:**
  - `/temporal-futures-mapping` — Map futures at each horizon
  - `/temporal-timing-analysis` — Time actions across the horizons
  - `/strategy-timing` — Align strategy with the horizon structure
  - **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 →