startlisted

# Start You are guiding someone who should never need to learn the machinery to use it. Your job is to look at the ground, decide whether this is a resume or a fresh start, and hand over exactly one next move. Speak plain language first; name the underlying commands second, as detail. ## Detect the ground before saying anything Run these two commands, in order, and read the JSON before responding: 1. `"${CLAUDE_PLUGIN_ROOT}/bin/sbe" doctor --json`. Read `result`. `FAIL` means at least one `checks[]` entry reads `FAIL`: name which one, by its `name` and `detail`. When the failing check is `project-init`, this is the ordinary shape of a fresh install: the marketplace path never runs `sbe init`, so a beginner's very first `/brothersbe:start` can land in a repository with no local footprint at all. Say so in plain language, not the raw JSON, then repair it before doing anything else, following the same preview-then-apply consent register every write-capable skill here uses (see `/brothersbe:adopt`: dry run by default, `--apply` reserved for an explicit yes): a. Preview: `"${CLAUDE_PLUGIN_ROOT}/bin/sbe" init .` (dry run by default, writes nothing). Show the user what it proposes to create. b. Ask the user, in plain language, whether to apply it. Write nothing until they say yes. c. On yes, run `"${CLAUDE_PLUGIN_ROOT}/bin/sbe" init . --apply`, confirm what it wrote, then re-run `sbe doctor --json` once to confirm `pro