feat(dx): add proactive-use triggers to agent descriptions

Rewrite planner/developer/task-runner descriptions with explicit "use
proactively" triggers and the model-mismatch condition, so the
orchestrating session self-routes to the right agent instead of relying
on CLAUDE.md prose being remembered each time.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
eho
2026-07-27 15:28:48 +02:00
co-authored by Claude Sonnet 5
parent 67170fbc84
commit 94cd0b82c2
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -1,6 +1,6 @@
---
name: task-runner
description: Run a simple, mechanical, read-only check and report the result — a test suite, `git status`, `grep`, verifying a file exists, lint/build output. Never for tasks needing design judgment or code edits — use `developer` or `planner` for those.
description: Run a simple, mechanical, read-only check and report the result — a test suite, `git status`, `grep`, verifying a file exists, lint/build output. Use PROACTIVELY, without waiting to be asked, whenever the current session is not already Haiku and the task is exactly one of these read-only checks. Never for tasks needing design judgment or code edits — use `developer` or `planner` for those.
model: haiku
disallowedTools: Edit, Write, NotebookEdit, Agent, Artifact, ExitPlanMode, EnterWorktree, ShareOnboardingGuide
---