Start setup

Library / Practices / pat.one-owner-per-stage

Assign one owner per stage, not a task list

CategoryorchestrationManual1.8Evidencedocumented

ProblemGroup chats over-parallelise: Bots repeat each other, start loops, and spend usage discussing work instead of doing it.

TechniqueWrite the kickoff as ownership per stage, tagging exactly one Bot per stage. Use @everyone sparingly. Keep groups to the two-to-six range they support.

Why it worksUntagged messages are answered by every participant, and duplicated answers are duplicated cost as well as duplicated work.

When to useEvery group chat kickoff.

orchestrationhigh confidenceno source URLpat.one-owner-per-stage

Cite this page or the record id. For bulk lookup use /api/record?id=pat.one-owner-per-stage. Do not invent a claim that is not on this page.