Delegate an outcome
Turn accepted intent into one bounded, owned and deliverable Assignment.
Use delegation whenever project-specific investigation, planning, coding, audit or review enters the Fleet. First and Second Mates coordinate; bounded Crewmates work in isolated project worktrees.
The supervisor first resolves the selected project workflow and existing domain charter. Durable intent becomes a Task; the active bounded outcome becomes one Assignment owned by one Agent. A ship Assignment must end through the project’s selected delivery path. A scout Assignment ends in a durable report and an exact inventory of unresolved Captain decisions.
A good outcome
Reproduce the checkout address defect, establish a falsifiable cause and return the smallest implementation boundary. Do not change project source.
That brief names the result, scope, evidence and authority. It does not prescribe every command or transfer credentials. If implementation follows, create a clean ship Assignment rather than turning the scout’s scratch changes into product code.
What you observe
PostgreSQL shows Task identity, Assignment owner and handoffs. Kubernetes and Herdr show the live worker. The worktree and Git show delivery. Completion is not credible until the selected durable artifact exists.
The delegation Skill owns acceptance, briefing, launch, steering, handoff and closure details.
Last updated on