Orient

Context. Gather first

Take session-id, branch, status, and recent-commits at -8, a deeper log than the save-point skills need, because this one synthesises a situation report. Probe commands, the one-command-per-call and treat-failure-as-unknown rules, and the $-expansion rationale for gathering at run time rather than pre-computing: ${CLAUDE_PLUGIN_ROOT}/reference/gather.md.

Orient

Purpose

Answer, in one read-only briefing: where do we stand, what are we doing, and why. The briefing draws on both the live conversation and the durable, off-thread state a conversation does not hold. Ledger files, handoff save-points, workflow checklists, running-retro ledgers, open pull requests and work-items, and git state. It orients; it changes nothing.

Why this is not the built-in /recap. /recap summarizes the conversation and auto-fires when you return to an idle terminal. It never reads the durable state on disk or the work running off this thread, and a skill cannot invoke it (built-in commands other than a small allowlist are not Skill-invocable). So this skill synthesizes the conversation summary inline and adds the durable + off-thread layer /recap cannot see. Reach for it when "what did the last session decide, and what is in flight right now" matters, not just "what did we just say."

Both halves of that boundary are verified 2026-09-06 against Claude Code 2.1.263. The auto-fire trigger comes from Session recap, which states that Claude Code shows the recap when you return to the terminal after stepping away and generates it once at least three minutes have passed since the last completed turn. The allowlist comes from Extend Claude with skills, which names /init and /security-review as built-in commands reachable through the Skill tool and /compact as one Claude cannot invoke that way. /recap is on neither list. Recheck when either page stops carrying those statements, or when a release note names /recap or the Skill-invocable command set.

What it reads (all read-only)

1. The conversation, the goal, the load-bearing decisions, and the direction established in this session. Synthesize these inline.
2. Durable memory-tier state. Resolve locations through the plugin binding (${CLAUDE_PLUGIN_ROOT}/reference/topic-docs.md), then read what exists, most-recent-first:
   • handoff save-points (<memory_dir>/handoffs/), the last session's in-flight snapshot; its own brief names where the work stood;
   • the workflow checklist (<memory_dir>/<slug>/), the stage ledger;
   • running-retro ledgers (<memory_dir>/running-retros/), accumulated in-flight findings. This skill only reads these; it never writes them, so the write-time runtime guards do not apply. Degrade quietly when a location is absent.
3. Repo + off-thread state, the git context gathered above, plus, when the tools are present and degrading gracefully when they are not: open pull requests (gh pr list for the current branch / author), open work-items (the consumer's tracker seam), and a glance at work running off this thread. Background tasks, monitors, subagents, and the other off-thread kinds (${CLAUDE_PLUGIN_ROOT}/reference/off-thread-work.md). Report the off-thread work at a glance. Do not inspect or recover it; that is /session-flow:keep-going.

The briefing. Four parts

Synthesize the reads into a short, current-state briefing:

• Goal / why. What we are trying to achieve and the reason, from the conversation and the handoff/ledger.
• Where we stand, the current state: branch, what is done versus pending, in-flight work, from the workflow checklist, handoff, and commits.
• Decisions made, the load-bearing decisions and their rationale so far, so they are not silently rediscovered or reversed.
• Direction / what's live, what is currently in motion: open PRs, off-thread work at a glance, and the intended thrust, without prescribing the next stage (that is workflow) or acting on it.

Ground every claim in a read this turn. Where the durable state and the conversation disagree, surface the discrepancy rather than picking one, and point at /session-flow:reanchor to verify which still holds.

Boundaries. Pick the right sibling

• Built-in /recap. Conversation-only, auto-fires. This skill adds durable + off-thread state and runs on demand.
• /session-flow:workflow. "What stage is next." Orientation reports where we stand; it does not prescribe the next step.
• /session-flow:reanchor. "Are my assumptions still true against live reality." Orientation synthesizes current state; it does not run a freshness/drift verification. When freshness is in doubt, it points here.
• /session-flow:keep-going. Recovers and continues off-thread work. Orientation reports off-thread work at a glance; it recovers nothing.
• /session-flow:retro. "What did we learn" (end-of-session scoring + codify). Orientation extracts no learnings and scores nothing.
• /session-flow:handoff. Writes a save-point and ends the session. Orientation writes nothing and ends nothing.

What this skill does NOT do

• Writes nothing, no files, no memory, no /clear. It is a read-only briefing that leaves state untouched.
• Does not verify freshness. It reports what the durable state says; confirming those claims still hold is /session-flow:reanchor.
• Does not recover off-thread work. It names what is in flight; inspecting and resuming it is /session-flow:keep-going.
• Does not prescribe the next stage; that is /session-flow:workflow.
• Does not score or codify; that is /session-flow:retro.
• Does not invoke the built-in /recap. Built-ins are not Skill-invocable; it synthesizes the conversation summary inline instead.

Gotchas

• The durable state can be stale; a handoff or ledger describes the moment it was written, not now. Report it as "the handoff claims X," and route a freshness check to /session-flow:reanchor rather than asserting it as current fact.
• Optional tools (gh, a tracker CLI) may be absent or unauthenticated. Degrade to the state you can read and say what you could not reach; never block the briefing on a missing optional source.
• Off-thread work is reported at a glance only. The moment the ask becomes "resume it" or "is it stuck," that is /session-flow:keep-going, not this skill.