feat: recommend plan→execute→verify pattern, relax subdivision guidance

- Plan instruction: add recommended architecture pattern (plan→execute→verify)
  with guidance that single execution expert is fine for straightforward roles
- Coordinator meta instruction: relax "break into focused units" to
  "only split when responsibilities are genuinely distinct"

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: FL4TLiN3

definitions/create-expert/perstack.toml

@@ -111,6 +111,12 @@ Constraints and rules the LLM cannot derive on its own, extracted from the user'
 ### Expert Architecture
 Delegation tree with role assignments. If the user specified a team name, use it exactly as the coordinator name. Delegate names describe function, not persona (/test, /verify, not /tester). For each expert: name, one-line purpose, role only.
 
+Recommended pattern: **plan → execute → verify**
+- A /plan expert expands context (requirements, domain knowledge, constraints) before work begins
+- An execution expert (or a few, if roles are genuinely distinct) does the actual work
+- A /verify expert checks the result with a hard signal (command + expected output)
+A single execution expert is fine when the role is straightforward. Only split execution into multiple experts when responsibilities are genuinely distinct — unnecessary subdivision adds latency and coordination overhead without improving quality.
+
 ### Test Query
 One comprehensive, realistic query that exercises the expert's full capability.
 

packages/runtime/src/messages/instruction-message.ts

@@ -44,8 +44,8 @@ function getCoordinatorMetaInstruction(): string {
     6. Aggregate results and clean up the workspace.
 
     Delegation guidelines:
-    - Be specific: include context, file paths, constraints, and expected output format. No vague delegations.
-    - Break large subtasks into focused units rather than overloading a single delegate.
+    - Be specific: include context, constraints, and expected output format. No vague delegations.
+    - A single delegate can handle a broad task if the role is straightforward. Only split into multiple delegates when responsibilities are genuinely distinct — unnecessary subdivision adds overhead without improving quality.
     - If no suitable delegate exists, use createExpert to create one, then addDelegate to register it.
 
     Workspace cleanup: