create-team

分类: 工具与效率 | 上传者: devstefancho | 下载: 0 | 版本: v1.0（最新）

与规划者和实施者队友一起创建一个代理团队，以进行规范驱动的开发。当用户说“创建团队”、“팀 생성”、“팀 만들어줘”、“代理团队”或想要在工作树会话中设置计划者+实施者工作流时使用。

更新日志: Source: GitHub https://github.com/devstefancho/claude-plugins

目录结构

当前层级: tree/main/agent-team-plugin/skills/create-team/

📁 templates/
- 📄 architect-prompt.md 1.9 KB
- 📄 devops-prompt.md 2.0 KB
- 📄 implementer-prompt.md 1.2 KB
- 📄 planner-prompt.md 1.4 KB
- 📄 researcher-prompt.md 1.6 KB
- 📄 reviewer-prompt.md 1.7 KB
- 📄 security-auditor-prompt.md 2.1 KB
- 📄 tester-prompt.md 1.8 KB
- 📄 ui-designer-prompt.md 1.9 KB
- 📄 work-guide.md 1.5 KB
📄 SKILL.md 3.2 KB

SKILL.md

---
name: create-team
description: Create an agent team with planner and implementer teammates for spec-driven development. Use when user says "create team", "팀 생성", "팀 만들어줘", "agent team", or wants to set up a planner+implementer workflow in a worktree session.
effort: medium
allowed-tools: Bash, Agent, SendMessage, TeamCreate, TaskCreate, TaskList, TaskUpdate, Read, AskUserQuestion
---

# Create Team

Creates a planner + implementer agent team for the current worktree session.

## Workflow

### Step 1: Determine team name

Run `git branch --show-current` to get the current branch name. Convert to kebab-case team name:
- Remove `worktree-` prefix if present
- Replace `+` with `-`
- Example: `worktree-feat+electron-app` → `feat-electron-app`

### Step 2: Create the team

Call `TeamCreate` with:
- `team_name`: the derived team name
- `description`: "Planner + Implementer team"

### Step 3: Spawn teammates (parallel)

Spawn both teammates **in parallel** using the Agent tool in a single message with two tool calls:

**Planner:**
- `team_name`: the team name
- `name`: "planner"
- `description`: "Planner - brainstorm and spec writing"
- `prompt`: Read the full content of [templates/planner-prompt.md](templates/planner-prompt.md) and pass it as the prompt
- `run_in_background`: true

**Implementer:**
- `team_name`: the team name
- `name`: "implementer"
- `description`: "Implementer - code and test writing"
- `prompt`: Read the full content of [templates/implementer-prompt.md](templates/implementer-prompt.md) and pass it as the prompt
- `run_in_background`: true

### Step 4: Loop setup

Send loop configuration via SendMessage:
- To "planner": If `/writing-specs` skill is available, "Run `/loop 10m /writing-specs update spec` to periodically check and update specs." Otherwise skip this loop setup.
- To "implementer": "After completing assigned work, check TaskList for new tasks. You can run `/loop 10m check TaskList for unassigned tasks and report to team-lead` to automate this."

### Step 5: Display work guide

Read [templates/work-guide.md](templates/work-guide.md) and display the content to the user.
Teammate colors are auto-assigned from a hardcoded palette and cannot be configured programmatically.

## Fallback

If teammate spawning via the Agent tool fails with `team_name` or another internal error in the current session (known issue anthropics/claude-code#40270):
1. Inform the user that team creation succeeded but teammate spawning failed in the current execution context
2. Suggest spawning teammates manually:
   - Open separate terminal windows
   - Run `claude` in each with the planner/implementer prompts
   - Use SendMessage for coordination
3. Do not claim the Agent tool is globally unavailable unless the session explicitly shows that tool is missing

## Notes

- Teammates are full Claude Code sessions, not subagents
- Both teammates can use all tools including Write, Edit, Bash
- Both can run skills like `/writing-specs`, `/loop`
- `/loop` is session-scoped and expires after 7 days
- Teammate colors are auto-assigned from hardcoded palette (red, blue, green, yellow...) — not configurable
- All communication flows through team-lead (planner <-> implementer direct messaging disabled by prompt rules)
- Teammate model defaults to standard Opus.

登录后下载/点赞/收藏 ❤ 5 | ★ 0

create-team

目录结构

SKILL.md

举报内容

提示