docs(council): target dedicated council agents by role
This commit is contained in:
@@ -120,13 +120,37 @@ Always multi-round (minimum rounds=2, default rounds=3 for this flow):
|
||||
|
||||
## Model Selection
|
||||
|
||||
Pick model tier based on topic complexity:
|
||||
Pick model tier based on topic complexity and role mission:
|
||||
|
||||
- **light** (casual brainstorm, simple pros/cons): default model for advisors and referee.
|
||||
- **medium** (architecture decisions, strategy): default model for advisors, stronger model for referee.
|
||||
- **heavy** (critical decisions, deep analysis): stronger model for all agents.
|
||||
- **light** (casual brainstorm, simple pros/cons)
|
||||
- advisors / freethinkers / arbiters: use dedicated council role agents on `litellm/gpt-5-mini`
|
||||
- referee / meta-arbiter: use dedicated synthesis agents on `openai-codex/gpt-5.4` (with configured fallbacks)
|
||||
- **medium** (architecture decisions, strategy)
|
||||
- advisors / freethinkers / arbiters: still use dedicated council role agents on `litellm/gpt-5-mini`
|
||||
- referee / meta-arbiter: use dedicated synthesis agents on `openai-codex/gpt-5.4`
|
||||
- **heavy** (critical decisions, deep analysis)
|
||||
- keep dedicated council role agents by profile
|
||||
- prefer stronger synthesis on `openai-codex/gpt-5.4`
|
||||
- if a specific council run is unusually high-stakes, the caller may override the spawned session model upward, but should preserve the dedicated council agent identity/role
|
||||
|
||||
The caller (main agent) determines tier before spawning.
|
||||
### Dedicated council agent roster
|
||||
|
||||
Personality mode:
|
||||
- `council-pragmatist`
|
||||
- `council-visionary`
|
||||
- `council-skeptic`
|
||||
- `council-referee`
|
||||
|
||||
D/P mode:
|
||||
- `council-d-freethinker`
|
||||
- `council-d-arbiter`
|
||||
- `council-p-freethinker`
|
||||
- `council-p-arbiter`
|
||||
- `council-meta-arbiter`
|
||||
|
||||
### Spawn rule
|
||||
|
||||
When invoking the council skill, explicitly target these dedicated agent ids via `sessions_spawn` instead of generic/default subagents. The caller (main agent) determines tier before spawning, but should preserve the role-specific council agent identity and use model overrides only when the mission/tier truly justifies it.
|
||||
|
||||
## Round-Specific Prompt Guidance
|
||||
|
||||
|
||||
Reference in New Issue
Block a user