Clarify subagent availability fallback

2026-05-29 10:55:20 +02:00
parent 689df3dbcb
commit 9d0f6a1295
1 changed files with 7 additions and 0 deletions
@@ -63,6 +63,13 @@ Do the refactoring pass in these distinct areas, first start a subagent for each
 2. Check for SOLID violations. Look for responsibilities that are mixed together, abstractions that are hard to replace or test, interface shapes that force unrelated dependencies, and code paths that require modifying stable code for each new variant.
 3. Check whether the implementation can be made simpler under KISS. Remove accidental abstractions, reduce branching, clarify names, and prefer the smallest structure that still supports the tested behavior and current spec.
 Do not say subagents are unavailable unless:
 1. tool discovery for "subagent", "delegate", and "agent" found no callable tool, or
 2. spawning a subagent returned a concrete tool error.
 In either case, report the exact discovery result or error.
 Preserve behavior during this pass and run the relevant tests again afterward.
 For Meeting Assistant, prefer verification through: