协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
share-config【开发与工程】Promote local config to a shared team config that can be committed to git.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Create a shared team config from your local config so collaborators can use the same pipeline, roles, and settings.
Verify .agenteam/config.yaml (or legacy agenteam.yaml) exists.
If not, tell the user: "No local config found. Run @ATeam init first."
If .agenteam.team/config.yaml already exists:
.agenteam.team/config.yaml.
Edit it directly to change team settings."Load the current config. Strip ALL personal-allowlist fields from every role:
model (personal preference)reasoning_effort (personal preference)system_instructions (may contain personal addenda)nickname_candidates (personal display preference)mcp_servers (local/private tool wiring)skills_config (local/private skill wiring)These fields are stripped because they should not become team policy.
The user can review and re-add team-relevant instructions manually.
Stripping model intentionally restores platform default inheritance for
collaborators and avoids sharing a pin that may be unavailable in their Codex
catalog.
If version is not "2", set it to "2".
mkdir -p .agenteam.team
Write the stripped config to .agenteam.team/config.yaml.
Print:
Team config created at .agenteam.team/config.yaml
What was stripped (personal-only fields):
- roles.*.model
- roles.*.reasoning_effort
- roles.*.system_instructions
- roles.*.nickname_candidates
- roles.*.mcp_servers
- roles.*.skills_config
Review it before committing. To customize:
- Team settings: edit .agenteam.team/config.yaml (tracked in git)
- Personal overrides: create .agenteam/config.yaml (gitignored)
Next steps:
git add .agenteam.team/
git commit -m "Add shared AgenTeam team config"
.agenteam/config.yaml can only change
model, reasoning_effort, system_instructions (append),
nickname_candidates, mcp_servers, and skills_config.allow_personal_override
in the team config.