will/swarm-zap
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(council): add executable roster and tier planner

Browse Source
This commit is contained in:
zap
2026-03-11 20:32:52 +00:00
parent 9e9f7996e9
commit e353be8814
4 changed files with 140 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
skills/council/SKILL.md
View File

@@ -196,6 +196,16 @@ Read `scripts/council.sh` for the orchestration logic.
For programmatic invocation, the main agent calls `sessions_spawn` directly
following the patterns above.
Long-term roster/tiering state now lives in executable data instead of prose only:
- `references/roster.json` — canonical dedicated council role -> agent -> default model mapping
- `scripts/council-plan.py` — resolves `mode` + `tier` into a concrete spawn plan
Before orchestrating a council run, resolve the plan first, for example:
- `python3 skills/council/scripts/council-plan.py --mode personality --tier light --pretty`
- `python3 skills/council/scripts/council-plan.py --mode dp --tier heavy --pretty`
Then use the returned `agentId` values in `sessions_spawn`. If `modelOverride` is null, preserve the dedicated agent's configured model. If present, apply the override only for that run.
## Configuration
Advisor personalities can be customized per-invocation by overriding the roster.