Found during dogfooding
Investigation tasks (read codebase, answer question) and implementation tasks (write code) both use the same dispatch mechanism. This worked because package boundaries didn't overlap, but it's luck — two experts editing the same file would conflict.
Proposal
Add a mode field to dispatch:
read-only (default for questions) — expert gets allowedTools without Write/Edit/Bashread-write (default for tasks) — full tool access, potentially with worktree isolation
Worktree isolation for write tasks would let multiple experts modify overlapping files safely. Each expert works in a git worktree, and the concierge/architect merges results.
Priority
Low — the package-boundary convention handles most cases. But for large refactors touching shared code, this becomes critical.
Found during dogfooding
Investigation tasks (read codebase, answer question) and implementation tasks (write code) both use the same dispatch mechanism. This worked because package boundaries didn't overlap, but it's luck — two experts editing the same file would conflict.
Proposal
Add a
modefield to dispatch:read-only(default for questions) — expert getsallowedToolswithout Write/Edit/Bashread-write(default for tasks) — full tool access, potentially with worktree isolationWorktree isolation for write tasks would let multiple experts modify overlapping files safely. Each expert works in a git worktree, and the concierge/architect merges results.
Priority
Low — the package-boundary convention handles most cases. But for large refactors touching shared code, this becomes critical.