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:
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: planner
|
||||
description: Design an implementation approach before code is written — architecture, edge cases, sequencing, trade-offs. Use for the design/Decisions phase of a WP, feature, or non-trivial fix. Does not write code; hands back a plan for the orchestrating session (or the developer agent) to execute.
|
||||
description: Design an implementation approach before code is written — architecture, edge cases, sequencing, trade-offs. Use PROACTIVELY, without waiting to be asked, whenever the current session is not already Opus and the task is: starting a new WP's Decisions block, an ambiguous bug whose root cause isn't yet known, or sequencing a multi-file/non-trivial change. Does not write code; hands back a plan for the orchestrating session (or the developer agent) to execute.
|
||||
model: opus
|
||||
disallowedTools: Edit, Write, NotebookEdit, Agent, Artifact, ExitPlanMode
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user