dispatch

Files (1)

• SKILL.md

SKILL.md (first lines)

# Dispatch

## When to use it

The user gave an explicit approved request.
Research, planning, investigation, and implementation all go through this skill.
Do not use it to do that work in the coordinator chat.

## Required inputs and access

The Persist skill, so the brief exists at `/workspace/sum/tasks/<id>/brief.md`.
The worker procedure memory.
A worker Bot whose worker procedure matches the project, or the ability to sign one on.
Cursor Cloud Agents available to that worker for isolated code work, when the task is software.

## Sequence of work

1. Write the brief from the user's words.
   Do not investigate first to fill gaps.
   Name the repository, the outcome, the scope, and how to check the result.
2. Persist the brief under a new task id.
3. Reuse existing role workers (Marketing, Security, Personal, Operations, Square, and similar) for matching non-software work.
   Only sign a new Sum worker when none fits.
   Do not recreate Square/Cleaner or Atlas.
   Reuse a software worker whose worker procedure already matches, or sign one on when none fits.
   Write the worker procedure memory into that Bot's description.
   Add that it reports outcomes and blockers to you against the task id, never to the user.
   When the user authorizes implementation after a verified investigation, cite the prior `report.md` / task id in the brief and forbid redoing the investigation.
4. Before you message the worker, append an `intended` line to `/workspace/sum/action-log.md`.
   If that intent and target already has `intended` or `done` in the last six hours, append `skipped-duplicate` and do not message them unless the user explicitly asked for this dispatch again.
   A repeated native message is not that ask.
   Then message the worker with the task id and the brief path.
   Ask for the outcome back against that id.
   After the message, append `done` or `failed`.
5. Tell the user which worker started, what it will deliver, and the task id.
6. End the turn.

## How to validate the result

`/workspace/sum/tasks/<id>/brief.md` exists and matches the user's words.
The worker Bot description says it is not the coordinator.
The coordinator chat contains no research, planning, investigation, or implementation of the request.

## What to return

The task id, the worker Bot, and the outcome the user should expect.
Then stop.

## What requires approval

Work starts only from an explicit user instruction or an already-approved task.
An unapproved issue is not approval.
Do not start a second execution because a native message arrived twice.

From douglasjarquin/sum, MIT.

More from douglasjarquin/sum