helplisted

# Help Orient the person first, list the machinery last. A flat command list is never the primary answer, because the person asking for help is exactly the person a flat list fails. ## What BrotherSBE is, said plainly Open with this, in your own words but with this content: BrotherSBE is a colleague that designs before it builds and refuses to claim what it did not check. It takes an outcome described in normal language, scores how risky the work is, requires a design proportional to that risk, executes against the design, and then proves the result with checks it names in advance. Where it could not check something, it says so instead of staying quiet. ## The lifecycle, one paragraph, no diagram Describe the flow as one plain paragraph: work starts with an intake that turns the described outcome into a tier, the tier decides which design artifacts are required, the design becomes a plan of tasks, the tasks get executed, gates and evidence checks verify the result, a review scores what the gates cannot, and the finished change goes to a human for the merge decision. Keep it to that register; do not introduce internal jargon the user has not asked for. ## The three entry points These are the only things a new user needs to remember: - `/brothersbe:start` to begin or resume anything. - `/brothersbe:next` to get the one recommended next action. - `/brothersbe:status` to see where the work stands. Recommend `/brothersbe:start` as the first move for anyone who is unsure.