How-tos

Start a delivery from Slack (members)

Explicitly: @YourEngineers deliver: add rate limiting to /login, or a phrase like "use a workflow to…", "run it through the workflow", "kick off a delivery workflow". No engineer name is needed. The workflow picks who does each step.
People for the human steps: add a line naming a step, e.g. QA: Tolu or Merge: @Ada, backup @Bola. The names must match the workflow's human steps; the person must be on the Members list.
Offered: when you ask an engineer for build or change work without saying how ("ada: add rate limiting…", "can you fix…"), the thread offers Deliver with workflow or Just do it here. Nothing runs until someone answers. Replying in the thread instead counts as "just do it here". Questions ("what does…", "how do I…") never get the offer.
Repo: give repo: owner/name (several: repo: a, b). Otherwise, if the team can reach more than one repo, you get a multi-select and Start (or reply repo: …). With two or more repos: Together, Separately or Let the lead decide (or reply together, separate or lead).
Name engineers: engineers: Ada, IG, or with Ada and IG reviewing. Only active engineers' names count. A name that can't do any step is refused when the delivery starts, with the reason.
Jira: jira: MOOR for a project, or jira: MOOR-12 to link an existing issue.
Everything about the delivery (handoffs, questions, the merge request, approvals, files) posts back into that thread. Replying there (with a mention) adds information for the engineer on the current step. Answering a question the delivery asked resumes it, and later steps get the answer too.
Owners for human steps can't be set from Slack yet. They come from the workflow, or use the portal form.