# shepherd-cli
`shepherd init --root PROJECT` creates the focused `.shepherd/runs/` workspace.
`shepherd lane --root PROJECT --run RUN --name LANE` adds a no-clobber lane plan,
ledger, and evidence directory. These commands do not select topology or create
a registry.
`shepherd doctor --host HOST --plugin-root ABS_PATH` inspects an installed
Claude, Codex, or Pi Shepherd carrier. It reports the helper and plugin versions,
required resources, the selected host hook, and optional `jq` availability.
It does not authorize tools or prove host trust and event delivery.
`shepherd handoff --host HOST --plugin-root ABS_PATH --context JSON_PATH`
renders the installed `templates/handoff.md` from a flat JSON object. The
current template uses `task`, `objective`, `artifact_root`, `status`,
`changed_paths_or_commit`, `verification`, `review`, `evidence_location`,
`remaining_work`, and `next_action`; `branch`, `base`, `candidate`, `rollback`,
and `date` are optional. Missing referenced fields fail before output. Default
output is stdout. `--output PATH` creates one complete file atomically and
refuses to replace different existing bytes; an identical retry leaves the
file untouched. Rendering does not verify the truth of the supplied result.
The CLI has no run registry, daemon, broker, or extracted runtime dependency.
Install from the Shepherd checkout with `cargo install --path crates/cli --locked`.
Use the installed `shepherd --version` to confirm the helper version before
running doctor against the actual plugin installation path.