Qcsd Ideation Swarm
proffesor-for-testing/agentic-qe
A skill your agent uses when running Quality Criteria sessions during PI/Sprint planning with HTSM v6.3, Risk Storming, or Testability analysis in the QCSD Ideation phase.
Bootstrap and run a multi-agent AI development team. An agent skill from boshi-xixixi/TraeSkill.
Install AI Team Orchestration
$ npx skills add boshi-xixixi/TraeSkill --skill ai-team-orchestration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boshi-xixixi/TraeSkill ai-team-orchestration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/boshi-xixixi/TraeSkill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.trae/Skills/.agents/skills/ai-team-orchestration .claude/skills/ai-team-orchestration && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ai-team-orchestration" agent skill from https://github.com/boshi-xixixi/TraeSkill/tree/main/.trae/Skills/.agents/skills/ai-team-orchestration into .claude/skills/ai-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-team-orchestration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/boshi-xixixi/TraeSkill/tree/main/.trae/Skills/.agents/skills/ai-team-orchestrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add boshi-xixixi/TraeSkill --skill ai-team-orchestration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boshi-xixixi/TraeSkill ai-team-orchestration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshi-xixixi/TraeSkill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.trae/Skills/.agents/skills/ai-team-orchestration .agents/skills/ai-team-orchestration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ai-team-orchestration" agent skill from https://github.com/boshi-xixixi/TraeSkill/tree/main/.trae/Skills/.agents/skills/ai-team-orchestration into .agents/skills/ai-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-team-orchestration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boshi-xixixi/TraeSkill --skill ai-team-orchestration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boshi-xixixi/TraeSkill ai-team-orchestration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshi-xixixi/TraeSkill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.trae/Skills/.agents/skills/ai-team-orchestration .cursor/skills/ai-team-orchestration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ai-team-orchestration" agent skill from https://github.com/boshi-xixixi/TraeSkill/tree/main/.trae/Skills/.agents/skills/ai-team-orchestration into .cursor/skills/ai-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-team-orchestration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/boshi-xixixi/TraeSkill.git --path .trae/Skills/.agents/skills/ai-team-orchestration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add boshi-xixixi/TraeSkill --skill ai-team-orchestration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boshi-xixixi/TraeSkill ai-team-orchestration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshi-xixixi/TraeSkill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.trae/Skills/.agents/skills/ai-team-orchestration .gemini/skills/ai-team-orchestration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ai-team-orchestration" agent skill from https://github.com/boshi-xixixi/TraeSkill/tree/main/.trae/Skills/.agents/skills/ai-team-orchestration into .gemini/skills/ai-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-team-orchestration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install boshi-xixixi/TraeSkill ai-team-orchestrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add boshi-xixixi/TraeSkill --skill ai-team-orchestration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boshi-xixixi/TraeSkill.git skills-src && mkdir -p .github/skills && cp -r skills-src/.trae/Skills/.agents/skills/ai-team-orchestration .github/skills/ai-team-orchestration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ai-team-orchestration" agent skill from https://github.com/boshi-xixixi/TraeSkill/tree/main/.trae/Skills/.agents/skills/ai-team-orchestration into .github/skills/ai-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-team-orchestration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boshi-xixixi/TraeSkill --skill ai-team-orchestration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boshi-xixixi/TraeSkill ai-team-orchestration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshi-xixixi/TraeSkill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.trae/Skills/.agents/skills/ai-team-orchestration .opencode/skills/ai-team-orchestration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ai-team-orchestration" agent skill from https://github.com/boshi-xixixi/TraeSkill/tree/main/.trae/Skills/.agents/skills/ai-team-orchestration into .opencode/skills/ai-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-team-orchestration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ai-team-orchestration- GitHub stars
- 276
- Token cost
- ~1.4k tokens
- SKILL.md length
- 479 words
- Files
- 5 (incl. references)
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- MIT
At a glance
Bootstrap and run a multi-agent AI development team. An agent skill from boshi-xixixi/TraeSkill.
- Works in 5 steps: Create PROJECT_BRIEF.md → Run a Brainstorm → Create Sprint Plans → …
- : starting a new software project with AI agents
- SKILL.md covers When to Use, Team Roles, Chat Architecture and Project Bootstrap, plus 3 more sections
- Calls git
What it does
AI Team Orchestration is an agent skill from boshi-xixixi/TraeSkill. Bootstrap and run a multi-agent AI development team. Use when: starting a new software project with AI agents, setting up parallel dev/QA teams, creating sprint plans, writing brainstorm prompts with distinct agent voices, recovering a project workflow, or planning sprints.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/anti-patterns.md`, `references/brainstorm-format.md` and `references/project-brief-template.md`).
It sits in Agent Workflows, covering Sprint planning and agile, Brainstorming and Multi-agent orchestration. The repository describes itself as: 为 Trae IDE 打造的全流程标准化 AI 开发技能库，内置调度分发与多角色研发技能，一键导入规范 AI 编码工作流 🚀. The licence is MIT.
When your agent uses it
- : starting a new software project with AI agents
- Setting up parallel dev/QA teams
- Creating sprint plans
- Writing brainstorm prompts with distinct agent voices
Example prompts
- “/ai-team-orchestration”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9cf38e6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
AI Team Orchestration loads about 1.4k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 479 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from boshi-xixixi/TraeSkill at commit 9cf38e6, republished under its MIT licence (© boshi-xixixi). 479 words, ~1,400 tokens.
Download SKILL.mdSave it as
.claude/skills/ai-team-orchestration/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- ai-team-orchestration
- description
- Bootstrap and run a multi-agent AI development team. Use when: starting a new software project with AI agents, setting up parallel dev/QA teams, creating sprint plans, writing brainstorm prompts with distinct agent voices, recovering a project workflow, or planning sprints.
AI Team Orchestration
When to Use
- Starting a new project that needs planning, development, testing, and deployment
- Setting up parallel AI agent teams (dev, QA, DevOps)
- Writing brainstorm prompts that produce real debate (not generic output)
- Creating sprint plans with cross-chat context survival
- Recovering from context overflow mid-sprint
Team Roles
| Agent | Name | Role | Focus |
|---|---|---|---|
| Producer | Remy | Sprint planning, coordination, merging PRs | Scope control, handoffs, issue triage |
| Product Designer | Kira | UX, mechanics, user experience | Fun factor, user flows, feature design |
| Visual/Art Director | Milo | CSS, animations, visual identity | Design system, polish, accessibility |
| Frontend Engineer | Nova | UI framework, state management, components | React/Vue/Svelte, client-side logic |
| Backend Engineer | Sage | API, database, auth, security | Server-side logic, infrastructure |
| DevOps Engineer | Dash | CI/CD, cloud deployment, pipelines | GitHub Actions, Azure/AWS/GCP |
| QA Engineer | Ivy | E2E tests, automation, playtesting | Playwright/Cypress, bug filing, sign-off |
Customize names and roles for your project. Not every project needs all roles.
Chat Architecture
The human (CEO) is the message bus between parallel chats:
┌────────────────────────────────────────┐
│ @ai-team-producer — Plans, merges │
│ NEVER writes code │
└────────────────┬───────────────────────┘
│ Human carries messages
┌──────────┼──────────┐
▼ ▼ ▼
┌──────────┐ ┌────────┐ ┌────────┐
│@ai-team │ │@ai-team│ │DevOps │
│-dev │ │-qa │ │(on │
│ │ │ │ │demand) │
│ Nova │ │ Ivy │ │ │
│ Sage │ │ │ │ │
│ Milo │ │ │ │ │
│ │ │feature/│ │feature/│
│ feature/ │ │qa-N │ │devops-N│
│ sprint-N │ └────────┘ └────────┘
└──────────┘Each team works in a separate VS Code window with its own clone:
git clone <repo> project-dev # Dev team
git clone <repo> project-qa # QA
git clone <repo> project-devops # DevOps (only when needed)Project Bootstrap
1. Create PROJECT_BRIEF.md
The single source of truth across all chats. See the project brief template.
Required sections (do not abbreviate):
- Project Overview
- Concept / Product Description
- Tech Stack
- Architecture (ASCII diagram)
- Key Files Map
- Team Roles
- Sprint Status (updated every sprint)
- Current State (rewritten every sprint)
- Security Rules
- How to Run Locally
- How to Deploy
- Cross-Chat Handoff Protocol — how context survives between chats
- Bug & Fix Tracking — GitHub Issues as single source of truth
- Multi-Repo Setup — separate clones, branch strategy, merge rules
2. Run a Brainstorm
See the brainstorm format. Key: name each agent explicitly with distinct personality and perspective. Require at least 2 genuine disagreements to prevent groupthink.
Show full SKILL.md (185 more words)Show less
3. Create Sprint Plans
See the sprint plan template. Every sprint gets:
docs/sprint-N/plan.md— prioritized tasks, success criteriadocs/sprint-N/progress.md— live tracker, enables recoverydocs/sprint-N/done.md— handoff doc written at sprint end
4. Execute Sprints
Read PROJECT_BRIEF.md, then read docs/sprint-N/plan.md. Execute Sprint N.
First: git pull origin main && git checkout -b feature/sprint-N
Close GitHub Issues in commits: "fix: description (Fixes #NN)"
Update docs/sprint-N/progress.md after each phase.
When done, push and create PR: git push origin feature/sprint-N
Follow Sections 12-14 of PROJECT_BRIEF.md.5. QA Sign-off
After dev merges, QA does a full playthrough:
Read PROJECT_BRIEF.md. You are Ivy (QA).
Sprint N is merged to main. Do full playthrough.
File bugs as GitHub Issues. Write docs/qa/sprint-N-signoff.md.Context Recovery
When a chat gets long (>100 messages), save state and start fresh:
Before closing:
- Update
docs/sprint-N/progress.mdwith current status - Update
PROJECT_BRIEF.mdsections 7+8 - Write
docs/sprint-N/done.md
Cold start prompt:
Read PROJECT_BRIEF.md and docs/sprint-N/progress.md.
Continue from where it left off.Anti-Patterns
See anti-patterns reference for the full list. Top 5:
| Don't | Do Instead |
|---|---|
| Rebase feature branches | Merge (rebase loses commits) |
| Producer writes code | Producer only plans, merges, files issues |
| Batch "fix everything" commits | One commit per fix with issue reference |
| Vague brainstorm prompts | Name each agent with distinct perspective |
| Keep bugs only in chat | File GitHub Issues (chat context dies) |
Tips for Better Results
- "Take your time, do it right" in prompts produces better output than rushing
- Test before merge — you playtest, file issues, dev fixes, then merge
- Run team consiliums before major sprints — each agent reviews the plan from their perspective
- Save lessons to memory after every milestone
© boshi-xixixi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in .trae/Skills/.agents/skills/ai-team-orchestration of boshi-xixixi/TraeSkill.
- SKILL.md
- references/anti-patterns.md
- references/brainstorm-format.md
- references/project-brief-template.md
- references/sprint-plan-template.md
Open the folder on GitHubat commit 9cf38e6
Compare with similar skills
AI Team Orchestration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| AI Team Orchestration this skillboshi-xixixi/TraeSkill | 276 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Qcsd Ideation Swarmproffesor-for-testing/agentic-qe | 495 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Clawteamwin4r/ClawTeam-OpenClaw | 1.5k | — | ~3.1k | Automated safety check: Pass | MIT | |
| AI Team Orchestrationgithub/awesome-copilot | 40k | — | ~992 | Automated safety check: Pass | MIT | |
| Design Orchestrationaiskillstore/marketplace | 433 | 6 repos | ~952 | Automated safety check: Pass | None | |
| Multi Agent Brainstormingaiskillstore/marketplace | 433 | 6 repos | ~1.4k | Automated safety check: Pass | None |
Similar skills
Clawteam
win4r/ClawTeam-OpenClaw
Multi-agent swarm orchestration. An agent skill from win4r/ClawTeam-OpenClaw.
- Official
AI Team Orchestration
github/awesome-copilot
Bootstrap and run a lightweight multi-agent development team.
Design Orchestration
aiskillstore/marketplace
Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.
Multi Agent Brainstorming
aiskillstore/marketplace
Simulate a structured peer-review process using multiple specialized agents to validate designs, surface hidden assumptions, and identify failure modes before implementation.
Idea Refinement
addyosmani/agent-skills
Guides a conversation that takes a vague idea through divergent and convergent thinking and ends in a markdown one-pager covering scope and assumptions.
More from boshi-xixixi/TraeSkill
All 16 skills in this repoArize Instrumentation
boshi-xixixi/TraeSkill
INVOKE THIS SKILL when adding Arize AX tracing or observability to an app for the first time, or when the user wants to instrument their LLM app or get started with LLM observability.
Dotnet MCP Builder
boshi-xixixi/TraeSkill
Build Model Context Protocol (MCP) servers in C/.NET against the current ModelContextProtocol 1.x NuGet packages.
Skill Creator
boshi-xixixi/TraeSkill
当用户需要创建新 Skill 或更新现有 Skill 时使用。此 Skill 提供技能创建的完整工作流指导，包括需求分析、编写规范、工程化构建、质量评估和迭代优化。
Trae Project Setup
boshi-xixixi/TraeSkill
Trae 项目规范化配置专家。用于快速初始化 Trae 项目配置文件、生成项目规则、用户偏好设置和 Skill 模板。当用户需要：(1) 初始化新项目的 Trae 配置 (2) 生成 .trae 目录结构 (3) 创建 USERPREFERENCES.md 用户偏好文件 (4) 创建 projectrules.md 项目规则文件 (5) 创建新的 Skill 模板 时使用此 Skill。
Web Coder
boshi-xixixi/TraeSkill
Expert 10x engineer with comprehensive knowledge of web development, internet protocols, and web standards.
Winapp CLI
boshi-xixixi/TraeSkill
Windows App Development CLI (winapp) for building, packaging, signing, debugging, and UI-automating Windows applications.
Related
Questions about AI Team Orchestration
What does AI Team Orchestration do?
Bootstrap and run a multi-agent AI development team. An agent skill from boshi-xixixi/TraeSkill. AI Team Orchestration is an agent skill from boshi-xixixi/TraeSkill. Bootstrap and run a multi-agent AI development team.
When should I use AI Team Orchestration?
AI Team Orchestration fits situations like: : starting a new software project with AI agents; setting up parallel dev/QA teams; creating sprint plans; writing brainstorm prompts with distinct agent voices.
How do I install AI Team Orchestration in Claude Code?
Run `npx skills add boshi-xixixi/TraeSkill --skill ai-team-orchestration -a claude-code`. Or copy the skill folder (.trae/Skills/.agents/skills/ai-team-orchestration in boshi-xixixi/TraeSkill) into .claude/skills/ai-team-orchestration in your project. Claude Code loads it when a task matches its description.
How do I install AI Team Orchestration in Codex?
Run `npx skills add boshi-xixixi/TraeSkill --skill ai-team-orchestration -a codex`. Or copy the skill folder (.trae/Skills/.agents/skills/ai-team-orchestration in boshi-xixixi/TraeSkill) into .agents/skills/ai-team-orchestration in your project. Codex loads it when a task matches its description.
Can I use AI Team Orchestration in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add boshi-xixixi/TraeSkill --skill ai-team-orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ai-team-orchestration, .gemini/skills/ai-team-orchestration, .github/skills/ai-team-orchestration and .opencode/skills/ai-team-orchestration in your project.
What does AI Team Orchestration need to run?
Going by SKILL.md and its folder, AI Team Orchestration needs the command-line tools its instructions call (git).
Does AI Team Orchestration access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is AI Team Orchestration safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does AI Team Orchestration use?
AI Team Orchestration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does AI Team Orchestration use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.
What are the alternatives to AI Team Orchestration?
Skills that share tags, products or a category with AI Team Orchestration: Qcsd Ideation Swarm (proffesor-for-testing/agentic-qe, 495 stars), Clawteam (win4r/ClawTeam-OpenClaw, 1.5k stars), AI Team Orchestration (github/awesome-copilot, 40k stars) and Design Orchestration (aiskillstore/marketplace, 433 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains AI Team Orchestration?
boshi-xixixi (a GitHub user) maintains it in boshi-xixixi/TraeSkill, which has 276 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on May 12, 2026.
Source: boshi-xixixi/TraeSkill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.