Ceo

CEO Agent - Direct Orchestration (v6.6.0)

When user requests software development, execute the following workflow:

Architecture Overview

v6.0 integrates Superpowers frameworks:

• Phase 0: Brainstorming for requirement exploration
• Phase 3.5: Git worktrees for workspace isolation
• Phase 4: Subagent-driven development with two-stage code review
• Phase 4.5: TDD enforcement
• Phase 5: Parallel agent dispatch for independent test failures

Key principles:

1. 流程自洽：Ensure workflow is complete, non-redundant, and naturally connected
2. 保留自动化：Retain maximum automation, only key checkpoints require human confirmation
3. 符合规范：Follow Claude Skill standards, prioritize Claude Code CLI native capabilities

---

Step 1: Initialize State Files

⚠️ NOTE: CEO agents are already installed as part of the ceo-skills plugin. No agent verification or installation is required.

Note: The Write tool will automatically create the .claudedocs directory if it doesn't exist.

Write initial task plan using Write tool

Create .claudedocs/task_plan.md with the following content:

# 任务计划

## Workflow配置 🆕 v6.5.0
- 执行模式: 待定（Step 1.5选择）
- 自动流转: 待定

## 用户需求
{USER_INPUT}

## 工作区配置
🔧 v6.5.0: 在阶段3.5创建Git Worktree后填充
- 工作区类型: Git Worktree
- 项目路径: 待定（阶段3.5创建）
- Git 分支: 待定（阶段3.5创建）

## 当前阶段
初始化

## 阶段进度
- [ ] 阶段0: 需求探索（brainstorming）
- [ ] 阶段1: 需求澄清（产品经理）
- [ ] 阶段2: 产品设计（UI/UX设计师）
- [ ] 阶段3: 架构设计（系统架构师）
- [ ] 阶段3.3: 平台决策（Web/Mobile/Both）🆕
- [ ] 阶段3.5: 工作区准备（git-worktrees）🔧 v6.5: 解决权限问题
- [ ] 阶段4: 开发实现（并行：Web+Mobile）🆕
- [ ] 阶段5: 测试验证（测试工程师-并行修复）
- [ ] 阶段6: 交付部署（市场营销师）

## 全局目标
1. 理解并澄清用户需求
2. 设计符合用户期望的产品
3. 实现高质量、可维护的代码
4. 确保充分测试和验证
5. 交付完整的文档和部署方案

---

Step 1.5: 选择Workflow执行模式 🆕 v6.5.0

Purpose: 在开始workflow前，让用户选择执行模式。

模式说明

• 🤖 自动模式（推荐）：完全自动化执行，跳过所有确认检查点，适合快速原型开发
• 👤 交互模式：在关键阶段暂停，等待用户确认，适合重要项目

Execution

Use AskUserQuestion tool:

Question: "选择CEO Workflow执行模式："
Header: "⚙️ Workflow模式配置"
Options:
  - label: "🤖 自动模式（推荐）"
    description: "完全自动化执行，跳过所有确认检查点，适合快速原型开发"
  - label: "👤 交互模式"
    description: "在每个关键阶段暂停，等待用户确认，适合重要项目"

Save user selection to task_plan.md:

If user selects "🤖 自动模式":

Edit file: .claudedocs/task_plan.md
Replace: "## Workflow配置\n- 执行模式: 待定（Step 1.5选择）\n- 自动流转: 待定"
With:
"""
## Workflow配置
- 执行模式: 自动模式
- 自动流转: 启用
- 确认检查点: 跳过
"""

If user selects "👤 交互模式":

Edit file: .claudedocs/task_plan.md
Replace: "## Workflow配置\n- 执行模式: 待定（Step 1.5选择）\n- 自动流转: 待定"
With:
"""
## Workflow配置
- 执行模式: 交互模式
- 自动流转: 禁用
- 确认检查点: 启用
"""

Display confirmation message:

═════════════════════════════════════════════════════════════
✅ Workflow模式已配置
═════════════════════════════════════════════════════════════

执行模式: {用户选择的模式}
{if 自动模式} 🤖 自动模式：将自动流转到所有阶段，无需手动确认
{if 交互模式} 👤 交互模式：将在关键阶段等待您确认

📋 下一步: Phase 0 - 需求探索

Proceed to Step 2 (Phase 0).

• Git 分支: 待定（阶段3.5创建）

当前阶段

初始化

阶段进度

• [ ] 阶段0: 需求探索（brainstorming）
• [ ] 阶段1: 需求澄清（产品经理）
• [ ] 阶段2: 产品设计（UI/UX设计师）
• [ ] 阶段3: 架构设计（系统架构师）
• [ ] 阶段3.3: 平台决策（Web/Mobile/Both）🆕
• [ ] 阶段3.5: 工作区准备（git-worktrees）🔧 v6.5: 解决权限问题
• [ ] 阶段4: 开发实现（并行：Web+Mobile）🆕
• [ ] 阶段5: 测试验证（测试工程师-并行修复）
• [ ] 阶段6: 交付部署（市场营销师）

全局目标

1. 理解并澄清用户需求
2. 设计符合用户期望的产品
3. 实现高质量、可维护的代码
4. 确保充分测试和验证
5. 交付完整的文档和部署方案

### Initialize notes file
Create `.claudedocs/notes.md` with the following content:
```markdown
# 项目笔记

## 初始化
项目启动时间: [执行时自动记录]

---

Step 2: Detect Current Phase and Resume

⚠️ CRITICAL: Before starting any phase, check if there's an existing workflow to resume.

Check for existing task plan

Use Read tool to check if task plan exists:

Read file: .claudedocs/task_plan.md

If task_plan.md exists (Resume Mode)

1. Parse current phase: Read "## 当前阶段" section
2. Check progress: Read "## 阶段进度" to see completed phases
3. Jump to next phase: Use the mapping below

Phase mapping:

"初始化" OR "阶段0: 需求探索" → Go to Step 3 (Phase 0)
"阶段1: 需求澄清" → Go to Step 4 (Phase 1)
"阶段2: 产品设计" → Go to Step 5 (Phase 2)
"阶段3: 架构设计" → Go to Step 6 (Phase 3)
"阶段3.5: 工作区准备" → Go to Step 7 (Phase 3.5)
"阶段4: 开发实现" → Go to Step 8 (Phase 4)
"阶段5: 测试验证" → Go to Step 9 (Phase 5)
"阶段6: 交付部署" → Go to Step 10 (Phase 6)

Display resume message:

═════════════════════════════════════════════════════════════
🔄 恢复工作流
═════════════════════════════════════════════════════════════

检测到现有任务计划，将从 {CURRENT_PHASE} 继续执行。

Then jump to the appropriate step above.

If task_plan.md doesn't exist (Fresh Start)

Display initialization message:

═════════════════════════════════════════════════════════════
🚀 启动新的 CEO 工作流
═════════════════════════════════════════════════════════════

将创建新的任务计划并执行完整 6 阶段开发流程。

Proceed to Step 3 (Phase 0).

---

Step 3: Execute Phase 0 - 需求探索（Brainstorming）

🆕 NEW in v6.0: Integrate Superpowers brainstorming for requirement exploration.

Purpose

Before generating formal PRD, conduct conversational exploration to fully understand user requirements through dialogue.

Process

Follow the brainstorming process:

digraph phase0_brainstorming {
    rankdir=TB;
    start [label="用户输入模糊需求", shape=ellipse];
    context [label="检查项目状态\n（文件、文档、最近提交）", shape=box];
    questions [label="苏格拉底式提问\n（一次一个问题）", shape=box, style=filled, fillcolor="#e1f5ff"];
    approaches [label="提出2-3种方案\n（含权衡分析）", shape=box];
    design [label="分段展示设计\n（200-300词/段）", shape=box];
    validate [label="每段后验证\n'这看起来对吗？'", shape=diamond];
    doc [label="保存设计文档\n.claudedocs/phase0-design.md", shape=box];

    start → context;
    context → questions;
    questions → approaches;
    approaches → design;
    design → validate;
    validate → design [label="否，调整"];
    validate → doc [label="是"];
}

Key Rules

提问规则:

• 一次一个问题：不要用多个问题淹没用户
• 优先选择题：比开放性问题更容易回答
• 聚焦理解：目的、约束、成功标准

设计展示规则:

• 分段展示：每段200-300词
• 每段验证：展示后询问"这看起来对吗？"
• 灵活调整：如有不清楚，返回澄清

产出物:

• 设计文档：.claudedocs/phase0-design.md
• 包含内容：架构、组件、数据流、错误处理、测试策略

Execution

⚠️ DO NOT use AskUserQuestion tool - brainstorming is a natural conversational process.

Invoke the brainstorming skill (from superpowers), execute it, then continue to Phase 1.

After brainstorming completes, save design document to:

.claudedocs/phase0-design.md

Then update task_plan.md to mark Phase 0 as completed:

Edit: Replace "- [ ] 阶段0: 需求探索（brainstorming）"
With:  "- [x] 阶段0: 需求探索（brainstorming）"
Edit: Replace "## 当前阶段\n初始化"
With: "## 当前阶段\n阶段0: 需求探索（完成）"

Proceed to Phase 1.

═════════════════════════════════════════════════════════════
✅ Phase 0 完成 - 需求探索
═════════════════════════════════════════════════════════════

📄 设计文档: .claudedocs/phase0-design.md
📋 下一步: Phase 1 - 需求澄清（产品经理）

---

Step 4: Execute Phase 1 - 需求澄清（产品经理）

⚠️ MANDATORY: Read Previous Phase Output

Before executing this phase, you MUST read all previous outputs:

Read file: .claudedocs/phase0-design.md

This ensures you have complete context from Phase 0.

Update task plan current phase

Use Edit tool to update task_plan.md:

Replace: "## 当前阶段\n初始化"
With: "## 当前阶段\n阶段1: 需求澄清"

Call Product Manager agent

⚠️ IMPORTANT: Execute the following steps in order to ensure the agent completes BEFORE the confirmation checkpoint.

Step 1: Launch agent

Task tool: Launch the ceo-product-manager agent with the following context:

## CEO任务上下文

### 用户输入
{USER_INPUT}

### 阶段0输出（NEW - 设计文档）
[使用Read工具读取 .claudedocs/phase0-design.md 内容]

### 你的任务
1. 基于阶段0设计文档生成产品需求文档（PRD）
2. 构建用户画像
3. 定义MVP范围
4. 识别未澄清的问题（如有）

### ⚠️ 关键约束 - 提问规则
- **最多提问5个问题**：降低用户认知负担
- **分批提问**：如果问题超过5个，分多次提问，每次最多5个
- **优先级排序**：先问最重要、最核心的问题

### 输出要求
- 输出完整的PRD文档到 .claudedocs/ceo-product-manager_result.md
- 包含用户画像、功能列表、优先级
- 如果有未问的问题，在文档末尾列出"待确认的问题"

Save the returned task_id as {PRODUCT_MANAGER_TASK_ID}

Step 2: Wait for agent completion

TaskOutput: Wait for {PRODUCT_MANAGER_TASK_ID}
Parameters: block=true, timeout=300000

⚠️ CRITICAL: DO NOT PROCEED until agent completes
⚠️ DO NOT proceed to confirmation checkpoint until this step completes

Step 3: Verify output file exists

Read file: .claudedocs/ceo-product-manager_result.md

⚠️ If file doesn't exist, agent failed - inform user and ask what to do

After agent completes and output is verified, proceed to confirmation checkpoint below.

Step 4.2: CONDITIONAL - User Confirmation Checkpoint 🆕 v6.5.0

⚠️ CONDITIONAL CHECKPOINT - 根据workflow模式决定是否需要确认

Check workflow mode first:

Read file: .claudedocs/task_plan.md

Extract:
  - 执行模式: (自动模式 | 交互模式)

If 执行模式 == "自动模式":

✅ 自动模式：跳过确认检查点

直接执行批准操作：
1. Use Edit tool to update task_plan.md:
   Replace: "## 当前阶段\n阶段1: 需求澄清"
   With: "## 当前阶段\n阶段2: 产品设计"
   Replace: "- [ ] 阶段0: 需求探索（brainstorming）"
   With: "- [x] 阶段0: 需求探索（brainstorming）"
   Replace: "- [ ] 阶段1: 需求澄清（产品经理）"
   With: "- [x] 阶段1: 需求澄清（产品经理）"

2. Display message:

═════════════════════════════════════════════════════════════ ✅ 自动模式：PRD已自动批准 ═════════════════════════════════════════════════════════════

🤖 执行模式: 自动模式 📄 PRD文档: .claudedocs/ceo-product-manager_result.md ✅ 状态: 已自动批准，继续下一阶段

📋 下一步: Phase 2 - 产品设计（UI/UX设计师）

3. Proceed to Step 5 (Phase 2).

If 执行模式 == "交互模式":

👤 交互模式：执行用户确认流程

⚠️ **CRITICAL**: You MUST pause here and wait for user confirmation before proceeding.

First, use Read tool to display PRD preview:

Read file: .claudedocs/ceo-product-manager_result.md Limit: 50 lines Display to user with formatted header: "📋 产品需求文档预览"

Then, use AskUserQuestion tool to get user confirmation:

Question: "请查看产品需求文档（PRD）并提供反馈。是否批准此PRD？" Header: "🎯 检查点 1 - 产品需求文档确认" Options:

• label: "✅ 批准PRD"

description: "PRD符合预期，批准并继续下一阶段"

• label: "📝 修改PRD"

description: "我有修改意见，需要调整PRD"

• label: "🔄 重做PRD"

description: "PRD不符合预期，需要重新澄清需求"

• label: "🛑 终止workflow"

description: "结束整个开发流程"

⚠️ **DO NOT PROCEED** until user selects an option.

Step 4.3: Process User Decision

If user selects ✅ 批准PRD:

1. Use Edit tool to update task_plan.md:

• Mark Phase 0 and Phase 1 as completed
• Update current phase to "阶段2: 产品设计"

1. Proceed to Step 5 (Phase 2).

═════════════════════════════════════════════════════════════
✅ Phase 1 完成 - 需求澄清
═════════════════════════════════════════════════════════════

📄 PRD文档: .claudedocs/ceo-product-manager_result.md
📋 下一步: Phase 2 - 产品设计（UI/UX设计师）

If user selects 📝 修改PRD:

1. Use AskUserQuestion to collect specific modification requests
2. Call Product Manager again with feedback
3. After revision completes, repeat Step 4.2 (confirmation checkpoint)

If user selects 🔄 重做PRD:

1. Use AskUserQuestion to collect new requirements
2. Call Product Manager for new round
3. After new PRD completes, repeat Step 4.2 (confirmation checkpoint)

If user selects 🛑 终止workflow:

1. Display termination message
2. Update task_plan.md with termination status
3. End workflow

---

Step 5: Execute Phase 2 - 产品设计

⚠️ MANDATORY: Read Previous Phase Outputs

Before executing this phase, you MUST read all previous outputs:

Read file: .claudedocs/phase0-design.md
Read file: .claudedocs/ceo-product-manager_result.md

This ensures you have complete context from Phase 0 and Phase 1.

Update task plan current phase

Use Edit tool to update task_plan.md:

Replace: "## 当前阶段\n阶段1: 需求澄清"
With: "## 当前阶段\n阶段2: 产品设计"

Call UI/UX Designer agent

⚠️ IMPORTANT: Execute the following steps in order to ensure the agent completes BEFORE proceeding.

Step 1: Launch agent

Task tool: Launch the ceo-ui-ux-designer agent with the following context:

## CEO任务上下文

### 用户输入
{USER_INPUT}

### 阶段0-1输出
[使用Read工具读取阶段0设计文档和阶段1 PRD]

### 用户对阶段0-1问题的回答
{USER_ANSWERS_PHASE0_1}

### 你的任务
1. 基于PRD设计用户故事
2. 设计交互流程
3. 设计视觉界面
4. 创建原型设计

### ⚠️ 关键约束 - 提问规则
- **最多提问5个问题**：降低用户认知负担
- **分批提问**：如果问题超过5个，分多次提问，每次最多5个
- **优先级排序**：先问最重要、最核心的设计问题

### 输出要求
- 输出完整的设计文档到 .claudedocs/ceo-ui-ux-designer_result.md
- 包含用户故事、交互流程、视觉设计

Save the returned task_id as {UI_UX_TASK_ID}

Step 2: Wait for agent completion

TaskOutput: Wait for {UI_UX_TASK_ID}
Parameters: block=true, timeout=300000

⚠️ CRITICAL: DO NOT PROCEED until agent completes

Step 3: Verify output file exists

Read file: .claudedocs/ceo-ui-ux-designer_result.md

⚠️ If file doesn't exist, agent failed - inform user and ask what to do

After agent completes and output is verified:

1. Use Edit tool to update task_plan.md: Mark Phase 2 as completed
2. Proceed directly to Phase 3 (no confirmation required).

═════════════════════════════════════════════════════════════
✅ Phase 2 完成 - 产品设计
═════════════════════════════════════════════════════════════

📄 设计文档: .claudedocs/ceo-ui-ux-designer_result.md
📋 下一步: Phase 3 - 架构设计（系统架构师）

---

Step 6: Execute Phase 3 - 架构设计

⚠️ MANDATORY: Read Previous Phase Outputs

Before executing this phase, you MUST read all previous outputs:

Read file: .claudedocs/phase0-design.md
Read file: .claudedocs/ceo-product-manager_result.md
Read file: .claudedocs/ceo-ui-ux-designer_result.md

This ensures you have complete context from Phase 0, 1, and 2.

Update task plan current phase

Use Edit tool to update task_plan.md:

Replace: "## 当前阶段\n阶段2: 产品设计"
With: "## 当前阶段\n阶段3: 架构设计"

Call System Architect agent

⚠️ CRITICAL: Execute the following steps in order to ensure the agent completes BEFORE the confirmation checkpoint.

Step 1: Launch agent

Task tool: Launch the ceo-system-architect agent with the following context:

## CEO任务上下文

### 用户输入
{USER_INPUT}

### 前期阶段输出
[使用Read工具读取所有前期输出文件]

### 用户回答
{USER_ANSWERS}

### 你的任务
1. 技术栈选型（前端、后端、数据库）
2. 系统架构设计
3. API规范设计
4. 数据模型设计

### ⚠️ 关键约束 - 提问规则
- **最多提问5个问题**：降低用户认知负担
- **分批提问**：如果技术决策问题超过5个，分多次提问
- **优先级排序**：先问最关键的技术选型问题

### 输出要求
- 输出完整的架构设计文档到 .claudedocs/ceo-system-architect_result.md

Save the returned task_id as {ARCHITECT_TASK_ID}

Step 2: Wait for agent completion

TaskOutput: Wait for {ARCHITECT_TASK_ID}
Parameters: block=true, timeout=300000

⚠️ CRITICAL: DO NOT PROCEED until agent completes
⚠️ DO NOT proceed to confirmation checkpoint until this step completes

Step 3: Verify output file exists

Read file: .claudedocs/ceo-system-architect_result.md

⚠️ If file doesn't exist, agent failed - inform user and ask what to do
⚠️ DO NOT proceed to confirmation checkpoint if file doesn't exist

After agent completes and output is verified, CHECK WORKFLOW MODE before proceeding.

⚠️ DO NOT PROCEED to Phase 3.5 until user confirms the architecture (交互模式) or auto-approves (自动模式)!

Step 6.1: CONDITIONAL - Architecture Confirmation Checkpoint 🆕 v6.5.0

🚨 CONDITIONAL CHECKPOINT - 根据workflow模式决定是否需要确认

Check workflow mode first:

Read file: .claudedocs/task_plan.md

Extract:
  - 执行模式: (自动模式 | 交互模式)

If 执行模式 == "自动模式":

✅ 自动模式：跳过确认检查点

直接执行批准操作：
1. Use Edit tool to update task_plan.md:
   Replace: "## 当前阶段\n阶段3: 架构设计"
   With: "## 当前阶段\n阶段3.3: 平台决策"
   Replace: "- [ ] 阶段3: 架构设计（系统架构师）"
   With: "- [x] 阶段3: 架构设计（系统架构师）"

2. Display message:

═════════════════════════════════════════════════════════════ ✅ 自动模式：架构已自动批准 ═════════════════════════════════════════════════════════════

🤖 执行模式: 自动模式 📄 架构文档: .claudedocs/ceo-system-architect_result.md ✅ 状态: 已自动批准，继续平台决策

📋 下一步: Phase 3.3 - 平台决策

3. Proceed to Step 6.3 (Phase 3.3).

If 执行模式 == "交互模式":

👤 交互模式：执行用户确认流程

🚨 **CRITICAL CHECKPOINT - MANDATORY USER CONFIRMATION REQUIRED**

You are at the Architecture Confirmation Checkpoint. You MUST execute this step before proceeding to Phase 3.5.

**Step 1**: Display architecture document preview using Read tool:

Read file: .claudedocs/ceo-system-architect_result.md Limit: 50 lines Display formatted header: "🏗️ 技术架构设计文档预览"

**Step 2**: Use AskUserQuestion tool to get user co

…

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [pyinx](https://github.com/pyinx)
- **Source:** [pyinx/ceo-skills-plugin](https://github.com/pyinx/ceo-skills-plugin)
- **License:** MIT

Install and usage instructions live in the source repository linked above.