Menü
Self-orient at session start — roadmap position, fleet state, what to do next
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Assess convergence, review session, write successor, close cleanly
Generate convergence-oriented roadmap specs
Autonomous roadmap execution with rich reporting
Run ad-hoc cause-routing diffusion whenever a roadmap node's REALIZED value falls short of its PROJECTED value — not only on RED/AMBER/BLOCKED, but on a GREEN that under-delivered (a shallow green). Identifies actual cause vs assumed cause, enumerates recovery axes, dispatches a non-symbolic recovery worker, and accepts the shortfall only when every axis yields a cited empirical zero. The general roadmap diffusion trigger; project-agnostic. Sibling to /core-loop · /cross-page-sweep · /diffuse-the-pipeline. Supersedes the narrower diffuse-on-not-green, which fired only on non-green and missed the shallow green entirely.
Author the boot prompt — capture session-tacit cognitive stance before context dies
| name | roadmap-orient |
| description | Self-orient at session start — roadmap position, fleet state, what to do next |
| user-invocable | true |
🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪
First thing every session. Find out where you are before you do anything.
roadmap orient --note "session start"
This is the source of truth. Auto-detects fleet.json for cross-repo state. Never infer position from git log or file inspection — orient returns it.
cat .roadmap/heads/r<N>.boot.md # round-scoped · N from current dag-id prefix
ls .roadmap/heads/r*.boot.md # all rounds chronologically
The boot prompt is the cognitive cartridge — round-scoped (one per round, not per DAG). Carries Stance (drift-prevention, dead ends, register, user concerns), Watch (things to flag), and Trajectory (prior session's outcome streak). Written by /roadmap-bootprompt at the end of the drafting session.
On first orient of a session, render r<N>.boot.md inline alongside the DAG topology. A fresh agent reading orient output cold sees both: where they are (DAG state) AND how the prior session wanted to think (boot).
If no r<N>.boot.md exists for the current round, note it — consider invoking /roadmap-bootprompt if cognitive context is worth preserving.
position which nodes are ready to work
briefs per-node: what to produce, what to consume, pattern
done how many nodes completed
remaining how many left
chainReady true = DAG complete, check successorProposal
chain iteration number, root intent, predecessor
suggestedSkill the next skill to invoke — follow it
If fleet.json exists (auto-detected):
repos per-repo status: active, complete, stalled, no-dag
activeDAGs all incomplete DAGs per repo (not just head.json)
globalFrontier all unblocked nodes across all repos
blockers cross-repo dependencies not yet satisfied
Parse the orient JSON and render the full DAG topology for the human. Show every batch, every node, completion status, and the current position. The human should see the whole shape at a glance.
┌──────────────────────────────────────────────────────────────┐
│ 🔮 api-platform — B3 of 11 │ 8/42 done │
├──────────────────────────────────────────────────────────────┤
│ B0 ( 1) init ✅ │
│ B1 ( 3) build-api ✅ │ build-auth ✅ │ build-cache ✅ │
│ B2 ( 4) wire-api ✅ │ wire-auth ✅ │ │
│ run-migration ✅ │ seed-data ✅ │
│ B3 (13) [🧪 deploy-frontend] [🧪 deploy-worker] │
│ [🧪 verify-contracts] [🧪 verify-routes] │
│ [🧪 smoke-tests] ←── you are here │
│ B4 ( 6) integration │ e2e │ load-tests │
│ B5 ( 2) staging │ canary │
│ B6 ( 1) term │
├──────────────────────────────────────────────────────────────┤
│ 📡 fleet: 5 frontier nodes across 2 repos │
└──────────────────────────────────────────────────────────────┘
Adapt the display to the DAG's actual shape. Wide batches get wrapped. Fleet data gets a footer. Color bars (🟥🟧🟨🟩🟦🟪) separate sections. Every scroll lands on something worth looking at.
For fleet orient, show per-repo status with their active DAGs:
┌─── FLEET ────────────────────────────────────────────────────┐
│ api api-platform ████████░░░░░░░░░░ B3 │
│ web web-frontend ██████████████████ DONE │
│ infra (no DAG) │
├──────────────────────────────────────────────────────────────┤
│ globalFrontier: 5 nodes (5 api, 0 web) │
│ blockers: deploy-worker waits on web build artifacts │
└──────────────────────────────────────────────────────────────┘
position has nodes? → /roadmap-auto (autonomous execution)
chainReady: true? → /roadmap-auto handles terminal inline
(assess · threads · present · successor)
no DAG? → /roadmap-spec (design one)
→ /roadmap-bootprompt (capture stance)
fleet has blockers? → surface which repos are blocking which
no r<N>.boot.md? → consider /roadmap-bootprompt if context worth preserving
orient → auto → (terminal inline) → spec → bootprompt → orient
every skill points to the next
orient is always the entry point and the re-entry point
After orient, read the repo's CLAUDE.md. It may have:
Orient tells you where. CLAUDE.md tells you how.
🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪🟥🟧🟨🟩🟦🟪
💀 position is truth · find out where you are before you do anything