Manage AI agent team members with skills, roles, and task delegation.
List all team member information:
python3 scripts/team.py list
Common scenarios:
Output example:
## Team Members
**Alice** ⭐ Leader - coordination,planning,decision-making
- agent_id: alice
- expertise: task breakdown, comprehensive decisions, agent coordination
- not_good_at: code development, investment analysis
**Bob** - Backend Developer - backend,API,database
- agent_id: bob
- expertise: Python,Go,PostgreSQL
- not_good_at: frontend,design
# Total: 2 member(s), Leader: Alice (alice)
Delegation Timing:
Delegation Context (what to pass):
When delegating, always provide:
Delegation Failover:
If teammate fails to complete:
Plan → Do → Check → Act
IMPORTANT: This is a continuous improvement cycle. If task is incomplete in Act phase, loop back to Plan.
Goal: Prepare thoroughly, avoid blind execution
Goal: Execute the plan while maintaining progress
Goal: Verify results against requirements
Goal: Summarize and decide next steps
Add a new member or update existing member information:
python3 scripts/team.py update \
--agent-id "agent-001" \
--name "Alice" \
--role "Backend Developer" \
--is-leader "true" \
--enabled "true" \
--tags "backend,api,database" \
--expertise "python,go,postgresql" \
--not-good-at "frontend,design" \
--load-workflow "true" \
--group "backend-team"
Parameters:
--agent-id: Member unique identifier (required)--name: Member name (required)--role: Role/position (required)--is-leader: Whether team Leader (required, true/false, only one Leader per team)--enabled: Enable status true/false (required)--tags: Tags, comma-separated (required)--expertise: Expertise skills, comma-separated (required)--not-good-at: Weak areas, comma-separated (required)--load-workflow: Whether to load workflow prompts (optional, true/false, default: true for leader, false for others)--group: Group name for categorization (optional, used for organizing team members)Clear all team data and reset to initial state:
python3 scripts/team.py reset
Output:
Team data has been reset.
⚠️ Warning: This operation is irreversible. All data in ~/.agent-team/team.json will be permanently deleted.
Team data is stored in ~/.agent-team/team.json, shared globally. Directory is auto-created if it doesn't exist.
# List team to find member with relevant expertise
python3 scripts/team.py list
# Look for matching tags/expertise in the output
Setting a new leader automatically removes leader status from the previous one:
python3 scripts/team.py update --agent-id "alice" --name "Alice" --role "Team Lead" --is-leader "true" --enabled "true" --tags "coordination,planning" --expertise "management,decision-making" --not-good-at "specialized-development"
Set --enabled "false" to disable without removing:
python3 scripts/team.py update --agent-id "bob" --name "Bob" --role "Backend Developer" --is-leader "false" --enabled "false" --tags "backend,api" --expertise "Python,Go" --not-good-at "frontend"
python3 scripts/team.py update --agent-id "charlie" --name "Charlie" --role "Frontend Developer" --is-leader "false" --enabled "true" --tags "frontend,ui" --expertise "React,TypeScript" --not-good-at "backend,database"
If ~/.agent-team/team.json doesn't exist, the script returns an empty team state (no error raised).
If the data file is corrupted, the script logs an error and returns an empty state:
[agent-team] Error loading team data: <error message>
Running update without required parameters:
error: the following arguments are required: --agent-id, --name, --role, --is-leader, --enabled, --tags, --expertise, --not-good-at
Only one leader can exist. Setting a new leader automatically removes leader status from the previous one:
Note: Removed leader status from <previous-leader-name>
共 6 个版本