ai-workflow-skill/skills/orch/references/worker-brief-template.md

Worker Brief Template

assets/orch-worker-brief renders a concrete prompt in this shape.

Use it when a leader has already dispatched a task and now wants to launch a worker sub-agent without hand-writing the thread handoff every time.

Use $inbox at INBOX_SKILL_PATH to act as ASSIGNED_TO on SQLite DB DB_PATH. Only coordinate through the bundled inbox CLI from the skill. Do not use ordinary chat to coordinate with the leader. Do not use orch.

You are assigned one existing attempt:
- run_id: RUN_ID
- task_id: TASK_ID
- attempt_no: ATTEMPT_NO
- assigned_to: ASSIGNED_TO
- thread_id: THREAD_ID
- execution_mode: analysis|code
- task_title: ...
- task_summary: ...
- base_ref: ...
- worktree_path: ...

Required workflow:
1. Fetch or inspect the assigned thread and claim exactly the listed thread_id.
2. Inspect the thread with show before making assumptions about the task body or payload.
3. Send one in_progress update when real work starts.
4. If blocked, send one precise blocked question with update --status blocked and then use wait-reply.
5. Finish with done on success or fail on failure.
6. Stop after reporting the handled thread_id and a concise outcome summary.

Rules:
- Do not claim any other thread.
- Keep all coordination in inbox messages, not ordinary chat.
- Do not change the assigned_to, thread_id, or worktree assignment yourself.
- If worktree_path exists, perform repository work only inside that path.

Notes

• The template is intentionally worker-only. Leader control stays with orch.
• The generated brief should be passed into a spawned worker sub-agent together with skills/inbox/.
• Keep the main-thread launch parameters in the leader workflow, not in the worker brief.
• execution_mode is part of the explicit dispatch contract and should come from the saved dispatch payload, not from local heuristics.