多智能体开发团队:协作式 AI 软件开发 - Openclaw Skills

作者:互联网

2026-03-29

AI教程

什么是 多智能体开发团队?

多智能体开发团队技能通过在 Openclaw Skills 中实现结构化的层级团队环境,改变了开发人员与 AI 交互的方式。该技能不再是与单一的通用助手交互,而是提供了一个专门的项目经理 (PM) 智能体和一个开发人员 (Dev) 智能体,两者协同工作。PM 智能体担任协调者,将您的高级目标转化为技术规范,而 Dev 智能体则专注于代码的实现、测试和版本控制。

通过利用这种多智能体架构,该技能确保了更高质量的输出和更好的项目组织。它旨在处理现代 Web 开发的复杂性,允许 AI 在规划和执行阶段分别保持上下文。这种方法显著减少了错误,并为原型和 Web 应用程序生成更整洁、更易于维护的代码库。

下载入口:https://github.com/openclaw/skills/tree/main/skills/chloepark85/multi-agent-dev-team

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

npx clawhub@latest install multi-agent-dev-team

2. 手动安装

将技能文件夹复制到以下位置之一

全局模式 ~/.openclaw/skills/ 工作区 /skills/

优先级:工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

请帮我使用 Clawhub 安装 multi-agent-dev-team。如果尚未安装 Clawhub,请先安装(npm i -g clawhub)。

多智能体开发团队 应用场景

  • 使用 Tailwind CSS 快速搭建 Next.js 和 React 应用程序。
  • 根据简单的文本描述构建功能性的 MVP 和原型。
  • 生成可重用的 TypeScript 组件库和 API 集成。
  • 管理需要独立规划和执行阶段的复杂编码任务。
  • 在 Openclaw Skills 生态系统中实施最佳实践的多智能体工作流。
多智能体开发团队 工作原理
  1. 用户向担任主管的 PM 智能体描述项目需求。
  2. PM 智能体分析需求并创建一个结构化的任务规范文档。
  3. PM 智能体生成 Dev 智能体,并为其提供技术约束和验收标准。
  4. Dev 智能体执行编码任务,初始化 Git 仓库,并编写必要的文件。
  5. PM 智能体审查生成的代码和交付物,以确保其符合项目目标。
  6. PM 智能体向用户报告完成情况,或在需要时启动最多三次的改进迭代。

多智能体开发团队 配置指南

首先,使用 CLI 安装该技能:

npx clawhub install multi-agent-dev-team

接下来,在您的 ~/.openclaw/config.yaml 文件中配置智能体,将 SOUL 定义链接到您偏好的 LLM 供应商:

agents:
  multi-agent-pm:
    soul: ~/.openclaw/skills/multi-agent-dev-team/agents/pm-agent/SOUL.md
    model: anthropic/claude-sonnet-4-5-20250929
    
  multi-agent-dev:
    soul: ~/.openclaw/skills/multi-agent-dev-team/agents/dev-agent/SOUL.md
    model: google/gemini-2.5-flash

通过与 PM 智能体聊天开始工作流:

openclaw chat --agent multi-agent-pm

多智能体开发团队 数据架构与分类体系

多智能体开发团队技能将项目数据组织成整洁、专业的目录结构。它利用特定的元数据和模板在 Openclaw Skills 会话之间保持状态:

组件 格式 用途
项目工作区 目录 包含所有源代码,通常在 ~/projects/ 或自定义的 cwd 下。
任务规范 Markdown 包含需求和验收标准的结构化移交文档。
版本控制 Git 每个项目都使用 Git 仓库进行初始化,以便进行更改跟踪。
会话历史 JSON/YAML 跟踪 PM 和 Dev 智能体之间的通信日志和迭代计数。
name: Multi-Agent Dev Team
description: 2-agent collaborative software development workflow for OpenClaw
homepage: https://ubik.systems
metadata: {"clawdbot":{"emoji":"??","requires":{"agents":["multi-agent-pm","multi-agent-dev"]}}}

Multi-Agent Dev Team

2-agent collaborative software development workflow for OpenClaw

Build complete software projects using AI agents that work together like a real development team.

What is this?

The Multi-Agent Dev Team skill provides a PM (Project Manager) and Dev (Developer) agent that collaborate to build software projects. You describe what you want, the PM breaks it down into tasks, and the Dev agent implements them.

Perfect for:

  • Landing pages and websites
  • Small web applications
  • Prototypes and MVPs
  • Code generation projects
  • Learning multi-agent workflows

Quick Start

1. Install the skill

npx clawhub install multi-agent-dev-team

2. Set up agents

The skill includes two pre-configured agents:

PM Agent (multi-agent-pm)

  • Handles project planning
  • Coordinates the Dev agent
  • Reports progress to you

Dev Agent (multi-agent-dev)

  • Implements code
  • Tests functionality
  • Commits to Git

3. Configure in ~/.openclaw/config.yaml

agents:
  multi-agent-pm:
    soul: ~/.openclaw/skills/multi-agent-dev-team/agents/pm-agent/SOUL.md
    model: anthropic/claude-sonnet-4-5-20250929  # or your preferred model
    
  multi-agent-dev:
    soul: ~/.openclaw/skills/multi-agent-dev-team/agents/dev-agent/SOUL.md
    model: google/gemini-2.5-flash  # faster for code generation

4. Start your PM agent

openclaw chat --agent multi-agent-pm

Usage Example

Building a Landing Page

You (Director):

Build me a Next.js landing page with hero section, features, and contact form. Use Tailwind CSS and TypeScript.

PM Agent:

I'll break this down into a clear task for the Dev agent. Starting now...

[Spawns Dev agent with detailed spec]

Dev agent is working on the project. I'll monitor progress and report back when complete.

PM Agent (later):

? Landing page completed!

Deliverables:

  • Next.js 14+ App Router project
  • Hero, Features, Contact sections
  • Fully responsive design
  • TypeScript + Tailwind CSS
  • Git repository initialized

Location: ~/projects/my-landing-page/

Ready for deployment. Would you like me to deploy to Vercel?

How It Works

Architecture

You (Director)
    ↓
PM Agent (Orchestrator)
    ↓
Dev Agent (Implementer)
    ↓
Working Code

Workflow

  1. You describe your project to the PM agent
  2. PM creates a structured task specification
  3. PM spawns Dev agent with the spec
  4. Dev implements the code
  5. PM reviews the deliverables
  6. PM reports completion (or requests revisions)
  7. Repeat steps 4-6 if needed (max 3 iterations)

Task Specification Format

The PM agent uses this template to communicate with Dev:

## Project: [NAME]
## Task: [ACTION]

## Requirements:
1. [Requirement 1]
2. [Requirement 2]

## Technical Constraints:
- [Constraint 1]
- [Constraint 2]

## Acceptance Criteria:
- [ ] [Criterion 1]
- [ ] [Criterion 2]

## Deliverables:
- [Deliverable 1]
- [Deliverable 2]

Supported Project Types

? Works Great

  • Next.js landing pages & apps
  • React components & SPAs
  • Node.js scripts & APIs
  • TypeScript projects
  • Static sites (HTML/CSS/JS)
  • Documentation sites

?? Limited Support

  • Complex backend systems (use Pro version)
  • Real-time applications
  • Multi-service architectures
  • Mobile apps
  • Large enterprise systems
  • Mission-critical production code without human review
  • Projects requiring specialized agents (use Pro version)

Configuration Options

Agent Models

PM Agent (orchestration):

  • anthropic/claude-sonnet-4-5 - Best reasoning
  • google/gemini-2.5-flash - Fast & efficient
  • openai/gpt-4o - Balanced

Dev Agent (code generation):

  • google/gemini-2.5-flash - Fast iteration (recommended)
  • anthropic/claude-sonnet-4-5 - Higher quality
  • openai/gpt-4o-mini - Budget-friendly

Workspace Configuration

Set a dedicated workspace for projects:

agents:
  multi-agent-pm:
    soul: ~/.openclaw/skills/multi-agent-dev-team/agents/pm-agent/SOUL.md
    model: anthropic/claude-sonnet-4-5-20250929
    cwd: ~/dev-projects  # All projects created here

Best Practices

1. Start Small

Don't ask for everything at once. Start with an MVP:

? Bad:

Build a full e-commerce site with user auth, payments, admin dashboard, and inventory management.

? Good:

Build a simple product landing page with hero, features, and signup form.

2. Be Specific

The more specific your requirements, the better the result:

? Vague:

Make a nice website.

? Specific:

Create a Next.js landing page with:

  • Hero section with CTA button
  • 3-column feature grid
  • Contact form with email validation
  • Tailwind CSS styling
  • Dark mode support

3. Iterate Incrementally

Build in phases:

Phase 1: Basic structure Phase 2: Add features Phase 3: Polish & deploy

4. Review Output

Always review the generated code before deploying. The agents are good, but human oversight is important.

5. Provide Examples

If you have a specific style or pattern in mind, share examples:

Build a landing page similar to https://example.com, but for [your product].

Troubleshooting

"Dev agent didn't complete the task"

Check:

  1. Was the task specification clear?
  2. Are required tools available (Node.js, Git)?
  3. Did the agent hit resource limits?

Solution:

  • Simplify the task
  • Check PM agent logs via sessions_history
  • Try again with clearer requirements

"Code doesn't work"

Check:

  1. Dependencies installed? (npm install)
  2. Environment variables set?
  3. Correct Node.js version?

Solution:

  • Ask PM agent: "The code has errors. Please review and fix."
  • The PM will spawn Dev again for corrections

"Task took too long"

Solutions:

  • Break into smaller tasks
  • Use faster model for Dev agent (gemini-2.5-flash)
  • Simplify requirements

Examples

Example 1: Simple Landing Page

You: Build a landing page for a SaaS product called "TaskFlow". 
Include hero, features (3 cards), and pricing table. Use Next.js 
and Tailwind CSS.

PM: Working on it... 
[2 minutes later]
PM: ? TaskFlow landing page complete! Ready for deployment.

Example 2: React Component Library

You: Create a reusable Button component library with variants 
(primary, secondary, outline) and sizes (sm, md, lg). Use 
TypeScript and class-variance-authority.

PM: Task received. Spawning Dev agent...
[3 minutes later]
PM: ? Button component library complete with Storybook examples.

Example 3: API Integration

You: Build a Next.js app that fetches and displays GitHub user 
profiles. Include search functionality and responsive cards.

PM: Starting development...
[4 minutes later]
PM: ? GitHub profile viewer complete with search and error handling.

Upgrading to Pro

Want more power? Upgrade to Multi-Agent Dev Team Pro ($49):

Pro Features

  • ?? 6 specialized agents: PM, Architect, Dev, QA, DevOps, BizDev
  • ?? Lobster pipelines: Automated workflows with approval gates
  • ??? Architecture design: Dedicated agent for system design
  • ? Automated QA: Code review & testing agent
  • ?? DevOps automation: Deployment & CI/CD setup
  • ?? Business planning: Market research & strategy agent
  • ?? Comprehensive guides: English + Korean setup docs

Get Pro →

Support

  • ?? Documentation: docs.openclaw.ai
  • ?? Discord: discord.com/invite/clawd
  • ?? Issues: github.com/openclaw/openclaw
  • ?? Email: support@ubik.systems

License

MIT License - See LICENSE file for details

Credits

Built by UBIK Collective

Powered by OpenClaw


Ready to build with AI agents? Install now:

npx clawhub install multi-agent-dev-team