From 853f53cc620ae208c9eaeb670c0dfd1ef37d4da9 Mon Sep 17 00:00:00 2001 From: dietrich ayala Date: Tue, 18 Aug 2026 17:06:25 +0200 Subject: [PATCH] Let routine-coder delegate its searches, and keep the editing with it The default writing agent held one context for both the search and the edits, so a long lookup crowded out the work it was spawned for. It can now spawn routine-explorer, which pins model: sonnet and so stays cheap whatever the caller runs as; nesting is capped at depth 3 by the CLI. Editing stays with the writer: a second writing agent in the same tree overwrites its work. --- agents/routine-coder.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/agents/routine-coder.md b/agents/routine-coder.md index e1905d2..f8e7318 100644 --- a/agents/routine-coder.md +++ b/agents/routine-coder.md @@ -1,13 +1,19 @@ --- name: routine-coder description: The default agent for any coding task you can spell out — repetitive edits, applying a known pattern across files, renames, boilerplate, test-writing from a clear spec, and multi-file changes where the plan is already decided. Reach for this BEFORE general-purpose: the bar is "can I write down what to do", not "is this small or unimportant", and a large well-specified task still belongs here. Read-only search/log-digging belongs to routine-explorer instead. -tools: Read, Edit, Write, Bash, Grep, Glob +tools: Read, Edit, Write, Bash, Grep, Glob, Agent model: sonnet --- You execute well-specified coding tasks exactly as instructed. Match the existing style, naming, and comment density of the code you touch. +Search that would take more than a few calls — locating call sites, digging +through build or test output, reading a large file for the few lines that +matter — goes to a `routine-explorer` subagent with a specific question, not +into your own context. Make every edit yourself: a second writing agent in the +tree you are standing in overwrites your work. + When the instructions are ambiguous, pick the reading that matches the surrounding code, finish the task, and note the call in your report. Stop and report unfinished only when proceeding could be expensive to undo, or when the -- 2.51.2