Team Configuration Save

Save the configuration of the currently running team as a snapshot, which is written to

.team-profiles/

in the project directory for reuse with

/team-load

Differences from team-init Auto-Save

	team-init Auto-Save	team-save Snapshot
Format	Template format (team_type + role code)	Snapshot format (full prompt)
Content	Initial configuration, references role definition files	Current actual state, self-contained
Purpose	Reconstruct team from role templates	Precisely restore modified teams
Identifier	`format: template`	`format: snapshot`

Save Process

Step 1: Identify the Team to Save

If the first parameter of

$ARGUMENTS

is not empty, use it as the team name. Otherwise, scan the

~/.claude/teams/

directory and list existing teams for the user to select.

If the directory does not exist or is empty, output a friendly prompt and exit:

There are no running teams currently.
- Use /team-init to create a new team

If there are teams, list them for selection:

AskUserQuestion:
  question: "Select the team to save"
  header: "Select Team"
  options:
    - label: "{team_name_1}"
      description: "{description_1}"
    - label: "{team_name_2}"
      description: "{description_2}"
    # ... up to 4
  multiSelect: false

Step 2: Read Team Configuration

Read

~/.claude/teams/{team_name}/config.json

and extract:

```
name
```
: Team name
```
description
```
: Team description
```
members[]
```
: List of members, extract the following for each member:
- ```
name
```
  : Member name
- ```
agentType
```
  : Agent type
- ```
prompt
```
  : Full prompt (if available)
- ```
model
```
  : Model
- ```
planModeRequired
```
  : If true, mode is "plan"; otherwise, "bypassPermissions"
- ```
cwd
```
  : Working directory
- ```
color
```
  : Color identifier

Extract team_type:

Attempt to infer the team type from the following sources (in priority order):

Check if there is a template-format configuration file with the same name in the project directory's
```
.team-profiles/
```
; if so, read its
```
team_type
```
Extract the
```
团队类型:
```
field from the
```
<project_context>
```
block in the member prompt
Match keywords from the description ("软件开发"→dev, "测试"→testing, "逆向"→reverse, "调试"→debug, "安全"→security, "CTF"→ctf, "运维"→ops, "讨论"→discuss)
If none of the above can determine it, set it to an empty string

Filter Rules:

Skip members with
```
agentType: "team-lead"
```
(team-lead is automatically created by the system, no need to save the prompt)
Only save members with the
```
prompt
```
field

Step 2.5: Collect Task Progress

Use the TaskList tool to get all tasks of the current team. Use TaskGet to obtain complete information for each task.

Extract the following for each task:

```
id
```
: Task ID (only used to record dependencies, will be reassigned during loading)
```
subject
```
: Task title
```
description
```
: Detailed description
```
activeForm
```
: In-progress description
```
status
```
: Status (pending / in_progress / completed)
```
owner
```
: Owner name (corresponds to the member's name)
```
blockedBy
```
: List of dependent task IDs

Note: If TaskList returns empty (no tasks), the

tasks

section will be an empty array, which is normal.

Step 3: Determine Save Name

If the second parameter of

$ARGUMENTS

is not empty, use it as the save name. Otherwise, use the team name by default.

AskUserQuestion:
  question: "Name for saving the configuration? (Will be saved to .team-profiles/{name}.yaml)"
  header: "Save Name"
  options:
    - label: "{team_name}"
      description: "Use team name"
    - label: "Custom name"
      description: "Enter in 'Other'"
  multiSelect: false

Step 4: Display Summary and Confirm

Team Snapshot Summary
--------------------
Team Name: {team_name}
Team Type: {team_type_name} (if available)
Team Description: {description}
Working Directory: {cwd}

Member List ({N} members):
  - {member_name} ({agentType}) [{model}]
  - ...

Task Progress ({M} tasks):
  - [completed] #{id} {subject} → {owner}
  - [in_progress] #{id} {subject} → {owner}
  - [pending] #{id} {subject} → {owner or "Unassigned"}
  ...

Save to: .team-profiles/{save_name}.yaml
--------------------

AskUserQuestion:
  question: "Confirm save?"
  header: "Confirmation"
  options:
    - label: "Save"
      description: "Save team snapshot"
    - label: "Cancel"
      description: "Abandon save"
  multiSelect: false

Step 5: Write Configuration File

Ensure directory exists:

Execute using the Bash tool:

bash

mkdir -p "{current working directory}/.team-profiles"

Overwrite Protection: If

.team-profiles/{save_name}.yaml

already exists:

Read the old file and extract the number of members and tasks

Display a difference summary in the confirmation step:

⚠ File already exists, will overwrite:
  Old configuration: {old_member_count} members, {old_task_count} tasks
  New configuration: {new_member_count} members, {new_task_count} tasks
Old file will be backed up as: .team-profiles/{save_name}.yaml.bak

Rename the old file to
```
.team-profiles/{save_name}.yaml.bak
```
before writing (use Bash:
```
mv
```
command)
If the
```
.bak
```
file also exists, directly overwrite the
```
.bak
```

Use the Write tool to create

.team-profiles/{save_name}.yaml

yaml

# Team Snapshot - Saved by /team-save
# Use /team-load {save_name} to directly load this configuration to create a team
# Save Time: {ISO 8601 timestamp}

format: snapshot
name: "{team_name}"
description: "{description}"
team_type: "{team_type}"           # Fill if extractable from member prompt, otherwise empty string
team_type_name: "{team_type_name}" # Same as above

members:
  - name: "{member_name}"
    agent_type: "{agentType}"
    model: "{model}"
    mode: "{mode}"              # bypassPermissions / plan / default, default is bypassPermissions
    cwd: "{cwd}"
    color: "{color}"
    prompt: |
      {full prompt content, using YAML multi-line string}

  - name: "{member_name_2}"
    agent_type: "{agentType}"
    model: "{model}"
    mode: "{mode}"
    cwd: "{cwd}"
    color: "{color}"
    prompt: |
      {full prompt content}

  # ... All non team-lead members

tasks:
  - original_id: "{original task ID, only used for dependency mapping}"
    subject: "{task title}"
    description: |
      {detailed task description}
    active_form: "{in-progress description}"
    status: "{pending / in_progress / completed}"
    owner: "{owner name, corresponds to name in members, empty string means unassigned}"
    blocked_by: ["{dependent original_id}", ...]  # Empty array means no dependencies

  - original_id: "2"
    subject: "..."
    description: |
      ...
    active_form: "..."
    status: "pending"
    owner: ""
    blocked_by: ["1"]

  # ... All tasks (including completed ones, to record full history)

Step 6: Output Result

Team snapshot saved to: .team-profiles/{save_name}.yaml
Contains configuration for {N} members (excluding team-lead) and {M} task records.

Use /team-load {save_name} to directly load this team.

Notes

Prompts may be very long (hundreds of lines), use YAML
```
|
```
multi-line string format for saving
Large File Writing Strategy: Snapshot files may exceed 150 lines (single limit of the Write tool). First use Write to write the file header and first few members (about 100-120 lines), then use the Edit tool to append the remaining members and tasks section
If the target file already exists, automatically back it up as
```
.bak
```
before overwriting, and display a difference summary in the confirmation step
Do not save the prompt for team-lead, as it is automatically created by the system during loading
Save the absolute path for cwd, which can be overwritten by the user during loading
Color Field: Only retained for records, the Task tool does not support setting colors, so it will not take effect during loading
The original_id of tasks is only used to record dependencies during saving; new IDs will be reassigned during loading and dependencies will be mapped
Completed tasks are also saved, and will be marked as completed directly during loading so the team knows which work has been done
Mode Detection Limitation: The config.json only has the
```
planModeRequired
```
boolean value;
```
false
```
is uniformly mapped to "bypassPermissions", and it is impossible to distinguish whether "default" or "bypassPermissions" was used during original creation. To precisely retain the "default" mode, manually edit the snapshot file after loading

team-save

NPX Install

Tags

SKILL.md Content (Chinese)