Commands and CLI

Everything is reachable from inside Claude Code as /orstrum:orstrum <subcommand>. The CLI underneath is there for scripts and for looking at a project from outside a session.

Slash commands

Command	What it does
/orstrum:orstrum start	The project interview. Writes spec.md, rules.md and policy.json into .orstrum/. Re-run it to change them.
/orstrum:orstrum report	Where the last session's budget went, shown as-is with one sentence on the biggest waste.
/orstrum:orstrum rollback	Restores the last working checkpoint and tells you what came back. Pro.
/orstrum:orstrum handoff	Asks the agent to write and store the handoff for the next session. Pro.
/orstrum:orstrum statusline	Shows the status-line entry for this machine and adds it to ~/.claude/settings.json if you agree.
/orstrum:orstrum license ork_…	Saves and verifies a Pro key. Pro tools are live in the next session.

CLI

The CLI is a single file in the installed plugin. Run it with Node from any project folder:

$node <plugin>/dist/cli.js doctor              # is capture working here? hooks, latest reading, Prescribe files, license
$node <plugin>/dist/cli.js sessions            # recent sessions and their share of the week
$node <plugin>/dist/cli.js report              # the latest session in detail
$node <plugin>/dist/cli.js analyze <file.jsonl> # a report from a Claude Code transcript alone
$node <plugin>/dist/cli.js license [ork_…]      # show or set the Pro key

report, sessions and doctor take --project <dir> to look at another folder. <plugin> is where Claude Code installed it; from a checkout it's plugin/ and pnpm orstrum <cmd> works too.

doctor

The first thing to run when something looks off. It checks that hooks are firing in this project, that the usage sampler has a recent reading (and shows it, to compare with /usage), which Prescribe files exist and which preset the policy matches, the license tier, and the tail of ~/.orstrum/hook.log.