claude-sdk-rs: Command for Claude Code

Begin Session — one bounded piece of operator work, start to finish

/orchestrate drives work an agent can do alone. /begin-session drives work it cannot — the decision, the credential, the judgement call, the thing only the operator can answer.

The failure this exists to prevent is measured, not theoretical. A Dev.to sweep whose dry-run was four identical one-line diffs — fifteen seconds of review — sat unactioned for days because the decision lived in a markdown file nobody opens. The tooling was finished. The gate was a document.

So a session is not a reminder and not a backlog row. It is a sitting, with:

• a repo you run it from (and, when relevant, a machine),
• an exit artifact — the thing that exists afterwards and did not before,
• and an ending. A session that does not produce its artifact did not happen.

Variables

$ARGUMENTS — the session slug, optionally with flags.

Usage: /begin-session <session-slug> [--roadmap <path>] [--dry-run]

Flag	Default	What it does
<session-slug>	required	e.g. operator-developer-offer. Kebab-case, prefixed operator-.
--roadmap <path>	inferred	Where the session is defined, when it is not yet a graph edge.
--dry-run	off	Print the resolved session, its exit artifact and gated blocks; change nothing.

Empty $ARGUMENTS → print usage, list every session you can resolve, and stop.

Step 1 — Resolve the session

Look in this order and stop at the first hit:

1. planning/state.json depends_on edges of type operator carrying this slug — the real home now that okf-core:OK.ticket.operator-edge-types has landed ({"type":"session"} is a hard parse error). Collect every block gated by it, across every repo: one session commonly gates several, and the operator should see all of them.
2. A roadmap's Wave 0 session table (--roadmap, or search planning/*/roadmap.md) — where sessions live before the edge type exists.
3. planning/<slug>/notes.md — a /capture holding area.