Back to Details

plan-with-team

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Plan With Team — Agent Team Planning Skill

团队规划 — Agent团队规划Skill

You orchestrate a 3-agent planning team that debates and refines an application plan before any code is written. The goal is to produce a battle-tested plan where architectural flaws, edge cases, and UX gaps have been challenged and resolved.
你将统筹一个由3个Agent组成的规划团队，在编写任何代码之前对应用方案进行讨论和优化。目标是产出一个经过充分验证的方案，其中架构缺陷、边缘情况和UX漏洞都已被排查并解决。

CRITICAL RULES

核心规则

  1. No code is written during planning. The output is a plan document only.
  2. The Skeptic writes NO artifacts. Their only job is to challenge and find flaws.
  3. Every agent must reference the relevant skills. Data Architect uses 
    dataverse-web-api
    , UX Designer uses 
    power-apps-code-apps
    . Load those skills for domain knowledge.
  4. The plan must be consolidated by the Lead into a single structured document before presenting to the user for approval.
  5. If agent teams are not enabled, fall back to single-agent structured planning using the same framework. Read 
    resources/fallback-mode.md
    .
  6. Schema creation can be parallelized. When implementation starts, reference 
    resources/parallelization.md
    in the 
    dataverse-web-api
    skill for the dependency graph. Multiple tables can be built simultaneously by separate agents.
  1. 规划阶段不编写任何代码。输出仅为方案文档。
  2. 质疑者不生成任何工件。他们的唯一职责是提出质疑，寻找缺陷。
  3. 每个Agent必须参考相关技能。数据架构师使用
    dataverse-web-api
    ，UX设计师使用
    power-apps-code-apps
    。加载这些技能以获取领域知识。
  4. 方案必须由负责人整合为单一结构化文档，然后提交给用户审批。
  5. 如果未启用Agent团队，则回退到使用相同框架的单Agent结构化规划。请阅读
    resources/fallback-mode.md
    。
  6. 架构创建可并行化。当开始实施时，请参考
    dataverse-web-api
    技能中的
    resources/parallelization.md
    获取依赖关系图。多个表可由不同的Agent同时创建。

The Team

团队组成

RoleAgent NameMandate
Data Architect
data-architect
Design tables, columns, relationships, option sets, security model
UX/Flow Designer
ux-designer
Design app module, forms, views, sitemap, user journeys
The Skeptic
the-skeptic
Challenge everything. Find security holes, edge cases, ALM issues, performance traps
角色Agent名称职责
数据架构师
data-architect
设计表、列、关系、选项集、安全模型
UX/流程设计师
ux-designer
设计应用模块、表单、视图、站点地图、用户旅程
质疑者
the-skeptic
对所有内容提出质疑，寻找安全漏洞、边缘情况、ALM问题、性能陷阱

Workflow

工作流程

Phase 1 — Gather Requirements (Lead)

阶段1 — 收集需求（负责人）

Before spawning the team, the Lead must understand:
  • Who uses this app? (personas/roles)
  • What data does it manage? (entities/relationships)
  • What are the key workflows? (create, approve, report, etc.)
  • What existing Dataverse tables/solutions already exist?
Ask the user these questions if the prompt is vague. Do NOT spawn the team until you have enough context to write meaningful spawn prompts.
在生成团队之前，负责人必须明确：
  • 谁会使用这个应用？（用户角色/画像）
  • 需要管理哪些数据？（实体/关系）
  • 核心工作流有哪些？（创建、审批、报告等）
  • 已存在哪些现有Dataverse表/解决方案？
如果用户的提示模糊不清，请询问上述问题。在获取足够上下文以生成有意义的Agent启动提示之前，不要生成团队。

Phase 2 — Spawn the Team

阶段2 — 生成团队

Spawn all three agents with detailed context. Each agent gets:
  • The user's requirements (from Phase 1)
  • Their role-specific instructions (from 
    resources/roles/
    )
  • Instructions to load the relevant domain skill
Spawn a teammate called "data-architect" with this prompt:
[Read resources/roles/data-architect.md and include its full content]

Spawn a teammate called "ux-designer" with this prompt:
[Read resources/roles/ux-designer.md and include its full content]

Spawn a teammate called "the-skeptic" with this prompt:
[Read resources/roles/the-skeptic.md and include its full content]
为三位Agent生成详细的上下文信息。每个Agent将获得：
  • 用户需求（来自阶段1）
  • 其角色专属的指令（来自
    resources/roles/
    ）
  • 加载相关领域技能的指令
Spawn a teammate called "data-architect" with this prompt:
[Read resources/roles/data-architect.md and include its full content]

Spawn a teammate called "ux-designer" with this prompt:
[Read resources/roles/ux-designer.md and include its full content]

Spawn a teammate called "the-skeptic" with this prompt:
[Read resources/roles/the-skeptic.md and include its full content]

Phase 3 — Parallel Design (Agents Work)

阶段3 — 并行设计（Agent工作）

  • Data Architect designs the schema and broadcasts their proposal
  • UX Designer designs the app structure and broadcasts their proposal
  • The Skeptic reads both proposals and challenges them with specific questions
Agents message each other directly to resolve issues. The Lead monitors but does NOT intervene unless agents are stuck or going in circles.
  • 数据架构师设计架构并发布其提案
  • UX设计师设计应用结构并发布其提案
  • 质疑者阅读两份提案并提出针对性问题进行挑战
Agent之间直接沟通以解决问题。负责人仅进行监控，除非Agent陷入僵局或偏离方向，否则不干预。

Phase 4 — Skeptic Review Round

阶段4 — 质疑者评审环节

The Skeptic performs a structured review using the checklist in 
resources/roles/the-skeptic.md
. They broadcast findings to both agents.
Data Architect and UX Designer must respond to every finding with either:
  • ACCEPTED — change incorporated into their design
  • REJECTED (reason) — justified pushback
质疑者使用
resources/roles/the-skeptic.md
中的清单进行结构化评审。他们会将评审结果发布给两位Agent。
数据架构师和UX设计师必须对每一项评审结果做出回应，回应方式为：
  • 已接受 — 将修改纳入设计
  • 已拒绝（理由） — 给出合理的反驳依据

Phase 5 — Consolidation (Lead)

阶段5 — 整合（负责人）

The Lead collects all three agents' final outputs and consolidates into the plan template defined in 
resources/plan-template.md
.
Present the consolidated plan to the user for approval.
负责人收集三位Agent的最终输出，并整合到
resources/plan-template.md
中定义的方案模板里。
将整合后的方案提交给用户审批。

Phase 6 — Handoff

阶段6 — 交接

Once approved, the plan document serves as the implementation spec. Each section maps directly to Dataverse Web API operations documented in the 
dataverse-web-api
skill.
Parallelization: Consider which implementation steps can run in parallel vs must be sequential. Multiple table agents can create their table + columns + views + forms simultaneously. Cross-cutting concerns (relationships, sitemap, app module) must be handled by the main agent after table agents complete. See the 
dataverse-web-api
skill's 
parallelization.md
resource.
方案获批后，该文档将作为实现规范使用。每个部分都直接对应
dataverse-web-api
技能中记录的Dataverse Web API操作。
并行化： 考虑哪些实施步骤可以并行执行，哪些必须按顺序执行。多个表Agent可以同时创建各自的表+列+视图+表单。跨领域事项（关系、站点地图、应用模块）必须在表Agent完成后由主Agent处理。请参阅
dataverse-web-api
技能中的
parallelization.md
资源。

Enabling Agent Teams

启用Agent团队

If the user hasn't enabled agent teams:
json
// Add to .claude/settings.json
{
  "env": {
    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
  }
}
Then restart Claude Code.
If agent teams are not available, use the fallback in 
resources/fallback-mode.md
.
如果用户尚未启用Agent团队：
json
// Add to .claude/settings.json
{
  "env": {
    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
  }
}
然后重启Claude Code。
如果Agent团队不可用，请使用
resources/fallback-mode.md
中的回退方案。