# Excursion Orchestration

> Orchestrate the excursion sequence — departure into unrelated domain, force-fit discoveries back to problem, launch springboard ideas.

- Skill: `yogsoth-ai/excursion-orchestration` (Agent Skill)
- Install (CLI): `npx skillmds@latest add yogsoth-ai/excursion-orchestration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yogsoth-ai/excursion-orchestration/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: yogsoth-ai (https://skillmd.com/u/yogsoth-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yogsoth-ai/excursion-orchestration

---


# Excursion Orchestration

Orchestrate the full excursion sequence from departure through force-fit to springboard launch.

## Stages

### Stage 1: Excursion Departure

Leave the problem entirely. Select an unrelated domain (nature, art, sport, cooking, music, etc.) and explore it deeply using excursion-departure SOP. The key is genuine immersion — not looking for connections yet.

### Stage 2: Force-Fit

Take the most interesting discoveries from the excursion domain and deliberately, forcefully connect them back to the original problem using force-fit SOP. Accept awkward connections — they often yield the best insights.

### Stage 3: Springboard Launch

Convert the force-fitted connections into "I wish..." or "How to..." springboard statements using springboard-launch SOP. Develop the most promising springboards into concrete solution concepts.

## Minimum Yield

| Metric | Floor |
|--------|-------|
| Excursion discoveries | ≥5 |
| Force-fitted ideas | ≥3 |
| Springboard statements | ≥3 |
| Concrete solutions | ≥2 |

## Available SOPs

| SOP | Role |
|-----|------|
| excursion-departure | Stage 1 — domain departure and exploration |
| force-fit | Stage 2 — force connections back to problem |
| springboard-launch | Stage 3 — convert to concrete solutions |
| direct-analogy-generation | Support — find analogies in excursion domain |
| synectics-synthesis | Post — synthesize excursion outputs |

<!-- BEGIN available-tables (generated) -->

## Available SOPs

Optional, no fixed order; the final leaf is always a sop.

| SOP | When to use |
| --- | --- |
| excursion-departure | Leave the problem entirely and explore an unrelated domain. Produces excursion domain discoveries for later force-fitting. |
| force-fit | Force-fit excursion discoveries back to the original problem. Deliberately create connections between unrelated findings and the challenge. |
| springboard-launch | Convert analogy insights into concrete feasible solutions. Transform abstract connections into actionable mechanisms. |

<!-- END available-tables (generated) -->