coord-delegatelisted

# Coordination Delegate This skill is the **assistant edge** of Edda coordination: a project assistant turns a user's request into one delegated job, keeps the conversation, and gets the result back without the user relaying messages or remembering run/session ids. The controller side of the same edge is `coord-orchestrate`; the runtime loop over a sealed control is `coord-run`. It is authored guidance over **existing** capability (`edda-pi launch`/`send`/`receipt`/`runs`/ `run-status`/`run-conversation`/`run-resume`, `edda task`). It adds no scheduler, no manager loop, no acceptance model, no role lock, and no human approval gate. Host and repository instructions retain precedence for safety, verification, review and merge authority. ## What this skill decides Use it when a user asks an assistant to get a **whole piece of background work** done, when a controller reports a result back, when a delivered job needs a **scoped change**, or when a user asks **where the work is** or **continue after an interruption**. | Situation | Action | |---|---| | New background job with a clear deliverable | Write one brief, launch one distinct controller, carry the assistant's return address | | A controller reports done/failed | Summarise for the user; separate delivery, content correctness and acceptance | | The user changes the scope of a delivered/running job | Route the change to that job's **existing** controller with an explicit change + receipt | | The user asks for current sta