maestro-work

maestro-work

The matched playbook (maestro recipe show <name>, chosen by Routing) owns the steps of a task. This skill owns what every playbook shares: the brief a writer receives, the rules it writes by, the handback it returns, and the record the holder keeps. A writer is a delegate subagent, a lane in a Herdr pane, or the main chat on a quickfix. Apply WORKFLOW.md for method rules; pause only the slice blocked by scope or authority.

Dispatch

When work is handed to a writer (a delegate subagent, or a lane in a Herdr pane in the room), send this envelope:

Objective: <observable outcome>
Owned scope: <paths or responsibility>
Excluded scope: <explicit non-goals>
Mutation: <no-write | write-bounded: paths>
Stop condition: <done or blocked boundary>
Lane: scout | decision | delivery | challenge | shadow
Evidence required: <proof and layer>

A tiny task may collapse the envelope to three lines, but it never drops Excluded scope or Mutation. Name the playbook and step the work serves, and point at files rather than pasting their content. Standing orders that apply to every writer of one run go in one file every brief points at.

• scout reads and reports state, never writes.
• delivery may write and is the only lane that holds the lease; a subagent's brief borrows the lane word but never takes the lease.
• decision investigates, compares, and recommends without writing.
• challenge breaks the premise or candidate and returns findings only, with no fixes or redesign.
• shadow runs beside the owner without writing and returns comparison evidence that is never a candidate or a work write lease.

No-write names the file boundary only. maestro dispatch accept and maestro handback file are the lane's own two writes and are never in the excluded scope, so a scout or shadow lane can still accept and return. A subagent opens no dispatch: the holder that briefed it reviews its diff and keeps the item.