A three-agent collaboration system for Cursor IDE that installs custom commands and enables team expansion.
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.
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
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.shThis 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
