onboardlisted

# /onboard — recon → draft → prove it answers Every role in this crew is told to hold the work to the standard in *your* repo's `README` / `CLAUDE.md`. Nothing produces that file. On a repo without a good one the whole crew quietly degrades to generic advice — and the failure is silent, because a vague context file still yields confident output. This order writes it, and **gates on a fresh agent being able to answer the crew's actual questions from the file alone**. Input (**$ARGUMENTS**): a path to a repo. Empty means the current one. **This is not `/document`.** The difference is the *audience*, not the topic. `/document` writes for **humans** and gates on a fresh reader completing a task. `/onboard` writes the **agent-facing contract** that every other order loads at run time, and gates on a fresh agent answering the crew's questions correctly. Same philosophy, different question — so neither forks the other. If what you want is a README or a tutorial, stop and run `/document`. --- ## Config (override only if the repo needs it) - `MODE` = `pr` (default) or `edit-in-place` — where the result lands. `pr` opens a worktree, a branch and a CI-gated PR rather than writing to the tree, reusing `/ship-issue`'s isolate stage and its commit-push-PR stage. This file is the contract every later run inherits, so it earns a diff and a human's eye before it lands; `edit-in-place` is an explicit request. `SURVEY` (`create` / `refresh`) is set by Stage 0 and describes what wa