A three-agent collaboration system for Cursor IDE and Qwen Code that installs custom commands and enables team expansion.
Now supports both Cursor IDE and Qwen Code platforms!
cursor-agent-team is a lightweight, IDE-integrated multi-agent collaboration framework that enables multiple specialized AI agents to work together within Cursor IDE. It belongs to:
- Academic: Multi-Agent System (MAS), Prompt Engineering Toolchain, Workflow Automation Framework
- Industry: Developer Tools (AI-enhanced), AI Agent Platform (lightweight), IDE Extension Framework
For detailed classification analysis, see Classification Analysis.
This framework installs three core Cursor commands (roles) into your project:
/discuss- Discussion Partner: The strategist who analyzes problems, explores ideas, and creates execution plans/crew- Crew Member: The executor who implements plans strictly according to specifications/prompt_engineer- Prompt Engineer: The HR and trainer who creates new roles (new Cursor commands)
With these three core roles installed, the team can operate. The Prompt Engineer can create additional roles as needed, allowing the team to expand.
- Lightweight: File-based architecture, no complex infrastructure required
- IDE Native Integration: Deeply integrated with Cursor IDE, seamless user experience
- Command-Driven: Commands as roles (Commands as Roles philosophy)
- Rule Management: Persistent rules via
.mdcfiles for consistent behavior - Extensible: Create custom roles via
/prompt_engineer - Workflow Automation: Complete discussion → planning → execution workflow
The strategist. Engages in discussions, analyzes problems, explores solutions, and generates executable plans. Does not modify project files directly—only provides strategies and plans.
The executor. Receives plans from the Discussion Partner and executes them step by step. Strictly follows plan specifications without deviation.
The HR and trainer. Creates and maintains new roles (Cursor commands). When you need a new specialized role, the Prompt Engineer helps create it as a new command file and rule file.
- Plan: Use
/discussto explore ideas and generate execution plans - Execute: Use
/crewto execute the plans - Expand: Use
/prompt_engineerto create new roles when needed
| Feature | cursor-agent-team | LangChain/AutoGen | GitHub Copilot |
|---|---|---|---|
| Positioning | IDE Extension Framework | General Application Framework | Code Completion Tool |
| Integration | IDE Native | External API/Library | IDE Plugin |
| Multi-Agent | ✅ Yes | ✅ Yes | ❌ No |
| Role System | ✅ Commands as Roles | ✅ Explicit Definition | ❌ No |
| Workflow | ✅ Discussion→Execution | ✅ Configurable | ❌ No |
| Lightweight | ✅ Yes | ❌ No | ✅ Yes |
| Extensible | ✅ Yes | ✅ Yes | ❌ No |
The framework also includes additional features that extend the core functionality:
A conversion tool for Spec-Kit workflow integration. Converts execution plans generated by /discuss into spec-kit formatted documents.
Purpose: When your project uses Spec-Kit for specification-driven development, this tool automatically converts Plan files into three spec-kit documents:
constitution.md- Project governance principles and development guidelinesspecify.md- Feature specification documentplan.md- Technical implementation plan
Usage:
/spec_translator PLAN-B-001
Workflow Integration:
- Use
/discussto generate an execution plan for a software development task - Use
/spec_translatorto convert the plan to spec-kit documents - Use spec-kit commands (clarify, tasks, etc.) to continue development
Note: This is an additional feature, not a core team role. It only processes software development tasks and automatically rejects non-software development plans.
For more information about Spec-Kit, visit the Spec-Kit repository.
/discuss
I want to add a new section about computational complexity to the paper.
What should be included?
After discussion, generate a plan:
/discuss
The discussion is ready, please generate the execution plan
The Discussion Partner generates a plan: PLAN-A-001
/crew PLAN-A-001
The Crew Member executes the plan step by step.
If you need a specialized role for a specific task:
/prompt_engineer
I need a role for generating figure captions
The Prompt Engineer creates:
.cursor/commands/figure_caption.md- A new command/figure_caption.cursor/rules/figure_caption_assistant.mdc- Rules for this role
You can now use /figure_caption in Cursor, just like the three core commands.
git submodule add https://github.com/thiswind/cursor-agent-team.git cursor-agent-team./cursor-agent-team/install.shThis installs the three core commands into .cursor/commands/ and rules into .cursor/rules/.
git submodule update --remote cursor-agent-team
./cursor-agent-team/install.sh./cursor-agent-team/uninstall.shgit submodule add https://github.com/thiswind/cursor-agent-team.git cursor-agent-team./cursor-agent-team/install_qwen.shThis installs the three core commands into .qwen/commands/ (TOML format) and context files into .qwen/context/ (Markdown format).
Note: The workspace at cursor-agent-team/ai_workspace/ is SHARED between Cursor and Qwen Code platforms. This allows seamless switching between platforms while maintaining the same discussion history, plans, and execution records.
git submodule update --remote cursor-agent-team
./cursor-agent-team/install_qwen.sh./cursor-agent-team/uninstall_qwen.sh- Cursor IDE: Uses
.cursor/directory with.mdcommands and.mdcrules - Qwen Code: Uses
.qwen/directory with.tomlcommands and.mdcontext files - Shared Workspace:
cursor-agent-team/ai_workspace/is shared between both platforms - Compatibility: You can install both versions in the same project - they work independently
This project is licensed under the GNU General Public License v3.0 (GPL-3.0).
See LICENSE file for details.
Current version: v0.3.0
See CHANGELOG.md for version history.
Contributions are welcome! Please feel free to submit a Pull Request.
thiswind
- GitHub: @thiswind