You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
refactor(multi-agent): move the multi-agent fenced config block to docs/conventions/multi-agent.yaml #9733
The multi-agent settings this repository keeps in the ```yaml config block of docs/conventions/multi-agent.md (ADR 0044 form) and .claude/multi-agent.yaml resolve from docs/conventions/multi-agent.yaml,
validated by a schema the plugin ships. The old location is read only when the YAML is absent, for one release.
The setup skill, if the plugin has one, writes the YAML.
Decisions
ADR 0064 Decision 1: a plugin's team settings live in one docs/conventions/<concern>.yaml, validated by a
JSON Schema at plugins/<plugin>/schemas/<concern>.schema.json (Decision 6), checked in CI by scripts/check-convention-yaml.sh (Decision 7). Script readers use the shared reader lib/parse-concern-value.sh.
ADR 0075: layers are plugin default < userConfig < team <home>/<concern>.yaml < personal <home>/<concern>.local.<ext>; every resolver reports the layer that supplied each value.
plugins/multi-agent/scripts/resolve-roles.sh and plugins/multi-agent/reference/config.md.
Done when
plugins/multi-agent/schemas/multi-agent.schema.json exists, and a resolve-roles.test.sh fixture holding docs/conventions/multi-agent.yaml resolves its values (this repository has no team block, so it adds no YAML file); scripts/check-convention-yaml.sh --check exits 0.
The reader's tests include: the YAML wins when both exist, the old location is read when the YAML is absent, and the resolver names the layer that supplied each value.
No skill body tells an agent to read or write the old location: git grep -n for it under plugins/multi-agent prints only compatibility-read code, its tests and changelog lines.
The PR body lists each migrated setting with its new home and schema.
Activity