S4h Temporal Futures Mapping

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'.

242 stars 25 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add human-avatar/skills-for-humanity --skill s4h-temporal-futures-mapping
Manual install
git clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git /tmp/skills-for-humanity
mkdir -p ~/.claude/skills
cp -r /tmp/skills-for-humanity/skills/s4h-temporal-futures-mapping ~/.claude/skills/s4h-temporal-futures-mapping

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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**
Read the full skill on GitHub

Details

Skill name
s4h-temporal-futures-mapping
Path
skills/s4h-temporal-futures-mapping/SKILL.md
License
MIT
Repo updated
15 July 2026

FAQ

What does the S4h Temporal Futures Mapping skill do?

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'.

How do I install the S4h Temporal Futures Mapping skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add human-avatar/skills-for-humanity --skill s4h-temporal-futures-mapping. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is S4h Temporal Futures Mapping popular?

It lives in human-avatar/skills-for-humanity, which has 242 GitHub stars and 25 forks, and is included in 1 curated skill list.

Related skills

S4h

242

human-avatar/skills-for-humanity

Master orchestration skill. Takes any situation in plain English, identifies the underlying goal, designs a multi-skill reasoning workflow, and executes it sequentially — feeding each skill's output into the next. Use when you say 'help me think through this', 'I need to figure out what to do', 'where do I start', or any time you want structured thinking applied end-to-end rather than routed to a single tool.

Testing & QAIn 1 list25

S4h Aesthetic

242

human-avatar/skills-for-humanity

Entry point for the aesthetic toolkit. Routes to the right aesthetic skill based on your situation. Use when you say 'aesthetic', 'check the design', 'does this feel right', 'is this elegant', 'is this too complex', 'what pattern is this', 'find the simpler version', or want an aesthetic lens applied without knowing which specific tool fits.

OtherIn 1 list25

S4h Aesthetic Coherence Check

242

human-avatar/skills-for-humanity

Tests whether the parts of something form a unified whole — finding the jarring inconsistencies that accumulate when different contributors work without a shared vision. TRIGGERS: 'coherence check', 'does this feel unified', 'something feels off', 'inconsistent', 'check the whole', 'does this hang together'.

Testing & QAIn 1 list25

Brainstorm

155

serpro69/claude-toolbox

TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to /kk:design; durable domain glossary/reference kits to /kk:model; implementation and fixes to /kk:implement. Not for nontechnical brainstorming.

Productivity & NotesIn 1 list30

S4h Strategy Alliance

242

human-avatar/skills-for-humanity

Maps parties, identifies natural allies and swing parties, and assesses alliance stability for coalition-building in competitive contexts. Triggers: 'build alliances', 'coalition building', 'who are my allies', 'manage stakeholders', 'political coalition', 'alliance strategy', 'who do I need on my side', 'get people on board', 'organizational politics'.

Productivity & NotesIn 1 list25

Implement

155

serpro69/claude-toolbox

TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency handling, review checkpoints.

Productivity & NotesIn 1 list30

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.