dispatch

What problem does it solve? Coordinators often end up doing research, planning, or implementation work themselves instead of delegating it, which blocks their availability and loses task traceability. This Skill enforces a clean handoff: every approved request becomes a persisted brief assigned to a dedicated worker Bot. ## Core Features & Use Cases - Brief Creation and Persistence: Writes a task brief from the user's exact words and stores it at /workspace/sum/tasks/<id>/brief.md before any work begins. - Worker Selection and Sign-On: Reuses existing role workers (Marketing, Security, Operations, and similar) for matching work, or signs on a new worker Bot with a worker procedure memory when none fits. - Guardrails Against Rework: Cites prior investigation reports when authorizing implementation, forbids redoing completed investigations, and prevents duplicate execution from repeated messages. - Use Case: A user asks to fix a failing login test. The coordinator writes the brief, persists it under a new task id, messages a software worker Bot with the brief path, and reports back which worker started and what it will deliver. ## Quick Start Ask the coordinator to dispatch an approved task, for example: dispatch a worker to investigate the failing login test in my repository and report the outcome against a task id.