bringing-coworker ยท diff
git:20260910.b01cff1 to git:20260911.fca2e0e
13 added, 16 removed. Audit A to A.
---
name: bringing-coworker
description: Use from an in-progress dispatched worker when the user asks to pull in a colleague, or a rule requires a second-agent review.
---
# Bring a coworker
- A coworker is one interactive agent you bring into your own Herdr tab and
- worktree for a second opinion or file-disjoint support. You integrate its
- result, and coworker nesting stops at this one level.
+ A coworker is one interactive agent you bring into your own Herdr tab and worktree for a second opinion or file-disjoint support.
+ You integrate its result, and coworker nesting stops at this one level.
## 1. Scope the second opinion
- Give the coworker one outcome that can run beside your current task. Default to
- review-only. A writing task names a disjoint repo-relative `--writable-path`
- scope.
+ Give the coworker one outcome that can run beside your current task.
+ Default to review-only.
+ A writing task names a disjoint repo-relative `--writable-path` scope.
Complete when the task is independently useful and its write scope is disjoint.
## 2. Start beside you
Use your canonical instruction path from the dispatch contract:
```bash
uv run --script "$HOME/.straw-boss/bin/run-straw-boss-script.py" \
--origin-root "${CLAUDE_PLUGIN_ROOT:-$PWD}" --prefer-installed \
--script dispatch-coworker.py -- \
--parent-instruction-path <your-instruction-path> \
--slug <unique-slug> [--name <short-name>] \
--agent-kind claude|codex --task "<user requirement and integrated context>" \
[--writable-path <repo-relative-path>]...
```
- The command authenticates your session, opens the coworker in this tab and
- worktree, injects its contract, and confirms delivery. Omit `--name` for a
- `<app>-coworker` handle derived automatically. Complete when it returns the
- coworker's pane and instruction path.
+ The command authenticates your session, opens the coworker in this tab and worktree, injects its contract, and confirms delivery.
+ Omit `--name` for a `<app>-coworker` handle derived automatically.
+ Complete when it returns the coworker's pane and instruction path.
## 3. Work with the user
- Point the user to the coworker pane. The coworker and user decide feedback and
- choose the specification, design, implementation, and the verification method
- inside the anchor you scoped for it; continue on your disjoint scope.
+ Point the user to the coworker pane.
+ The coworker and user decide feedback and choose the specification, design, implementation, and the verification method inside the anchor you scoped for it; continue on your disjoint scope.
- Complete when the coworker reports `done` or `failed`; parent and root
- coordinator receive that terminal event automatically.
+ Complete when the coworker reports `done` or `failed`; parent and root coordinator receive that terminal event automatically.
## 4. Integrate and close
- Integrate the reported result, then use [dispatching-work wrap-up](../dispatching-work/SKILL.md#wrap-up) for the coworker instruction. The shared tab and your own instruction remain active.
+ Integrate the reported result, then use [dispatching-work wrap-up](../dispatching-work/SKILL.md#wrap-up) for the coworker instruction.
+ The shared tab and your own instruction remain active.
Complete when the pane is closed and the coworker instruction is archived.