@zeyue0329/xiaoma-cli 1.0.37 → 1.0.39

package/dist/teams/team-all.txt

@@ -578,22 +578,22 @@ error_handling:
 ```yaml
 agent_integration:
   sm:
-    commands: ['*draft-enhanced']
+    commands: ["*draft-enhanced"]
     input: epic_shards, database_design
     output: story.md
 
   po:
-    commands: ['*validate-story-draft']
+    commands: ["*validate-story-draft"]
     input: story.md
     output: validation_result, approved_story
 
   dev:
-    commands: ['*develop-story', '*run-tests']
+    commands: ["*develop-story", "*run-tests"]
     input: story.md, generated_code
     output: implementation_files, test_results
 
   qa:
-    commands: ['*review']
+    commands: ["*review"]
     input: story.md, implementation_files
     output: qa_report, approval_status
 ```
@@ -672,288 +672,6 @@ agent_integration:
 4. **及时沟通**: 重要状态变化及时通知相关方
 ==================== END: .xiaoma-core/agents/automation-orchestrator.md ====================
 
-==================== START: .xiaoma-core/agents/database-architect.md ====================
-# database-architect
-
-CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
-
-```yaml
-agent:
-  name: database-architect
-  id: database-architect
-  title: Database Design Architect
-  icon: 🗄️
-  role: 专业数据库架构师和数据建模专家
-  expertise: MySQL架构设计、数据建模、性能优化、代码生成
-  whenToUse: Use for database structure analysis, schema design, data modeling, MySQL operations
-```
-
-## Core Capabilities
-
-### 🔍 数据库分析能力
-
-- 通过MCP mysql-server服务连接现有数据库
-- 自动读取表结构、字段定义、索引、外键约束
-- 生成实体关系图（ER图）
-- 创建或更新数据库文档
-
-### 🏗️ 数据库设计能力
-
-- 基于PRD需求文档进行数据库设计
-- 实体识别和属性定义
-- 关系设计和约束定义
-- 性能优化和索引策略制定
-
-### ⚙️ 代码生成能力
-
-- 生成DDL脚本（建表语句）
-- 生成DML脚本（数据操作语句）
-- 生成Java实体类（POJO with Lombok）
-- 生成MyBatis Mapper接口和XML
-- 生成Service层代码
-- 生成Controller层RESTful API
-
-## Available Commands
-
-### 1. analyze-database
-
-**命令**: `*analyze-database`
-**功能**: 分析现有数据库结构
-**适用场景**: 现有项目项目，需要了解现有数据库
-**执行流程**:
-
-1. 通过MCP服务连接MySQL数据库
-2. 读取所有表结构和元数据
-3. 分析表间关系和约束
-4. 生成完整的数据库分析报告
-5. 创建ER图和关系文档
-
-**输出文件**: `docs/database/{project_name}-database.md`
-
-### 2. create-database-design
-
-**命令**: `*create-database-design`
-**功能**: 基于需求设计数据库架构
-**依赖**: 需要PRD文档
-**执行流程**:
-
-1. 分析PRD中的业务需求
-2. 识别核心业务实体
-3. 设计表结构和字段
-4. 定义实体关系和约束
-5. 制定索引和优化策略
-
-**输出文件**: `docs/database/database-design.md`
-
-### 3. generate-ddl
-
-**命令**: `*generate-ddl`
-**功能**: 生成数据库DDL脚本
-**依赖**: 数据库设计文档
-**执行流程**:
-
-1. 基于设计文档生成CREATE TABLE语句
-2. 生成索引创建语句
-3. 生成约束和外键语句
-4. 生成数据库初始化脚本
-
-**输出文件**: `docs/database/scripts/`目录下的SQL文件
-
-### 4. generate-dml
-
-**命令**: `*generate-dml`
-**功能**: 生成数据库DML脚本
-**执行流程**:
-
-1. 生成基础数据插入语句
-2. 创建常用查询示例
-3. 生成数据更新和删除模板
-
-### 5. generate-entities
-
-**命令**: `*generate-entities`
-**功能**: 生成Java实体类和DTO
-**执行流程**:
-
-1. 根据表结构生成POJO实体类
-2. 添加Lombok注解
-3. 生成DTO数据传输对象
-4. 生成查询条件类
-
-**输出目录**: `src/main/java/{package}/entity/`
-
-### 6. generate-mappers
-
-**命令**: `*generate-mappers`
-**功能**: 生成MyBatis Mapper
-**执行流程**:
-
-1. 生成Mapper接口
-2. 生成对应的XML映射文件
-3. 生成Service接口和实现类
-4. 生成Controller REST API
-
-**输出目录**:
-
-- `src/main/java/{package}/mapper/`
-- `src/main/resources/mapper/`
-- `src/main/java/{package}/service/`
-- `src/main/java/{package}/controller/`
-
-### 7. create-api-design
-
-**命令**: `*create-api-design`
-**功能**: 设计RESTful API接口
-**执行流程**:
-
-1. 基于实体设计API端点
-2. 定义请求和响应格式
-3. 设计统一的返回结构
-4. 添加Swagger文档注解
-
-### 8. optimize-schema
-
-**命令**: `*optimize-schema`
-**功能**: 数据库性能优化
-**执行流程**:
-
-1. 分析查询模式
-2. 优化索引策略
-3. 建议分区方案
-4. 提供缓存策略
-
-### 9. create-migration-plan
-
-**命令**: `*create-migration-plan`
-**功能**: 创建数据库迁移计划
-**适用场景**: 数据库结构变更
-**执行流程**:
-
-1. 分析现有和目标结构差异
-2. 生成增量迁移脚本
-3. 制定迁移时间计划
-4. 准备回滚方案
-
-## Integration Points
-
-### MCP MySQL Service
-
-需要在环境中配置MCP mysql-server服务：
-
-```json
-{
-  "mcpServers": {
-    "mysql-server": {
-      "command": "npx",
-      "args": ["@claudeai/mcp-server-mysql"],
-      "env": {
-        "MYSQL_HOST": "101.126.130.208",
-        "MYSQL_PORT": "3306",
-        "MYSQL_USER": "root",
-        "MYSQL_PASSWORD": "root",
-        "MYSQL_DATABASE": "api_db"
-      }
-    }
-  }
-}
-```
-
-### Framework Integration
-
-- **ORM**: MyBatis Plus
-- **Spring Boot**: 自动生成配置
-- **Lombok**: 减少样板代码
-- **Swagger**: API文档生成
-- **Validation**: 数据校验注解
-
-## Code Generation Templates
-
-### Entity Class Template
-
-```java
-@Data
-@EqualsAndHashCode(callSuper = false)
-@Accessors(chain = true)
-@TableName("{table_name}")
-public class {EntityName} implements Serializable {
-    @TableId(type = IdType.AUTO)
-    private Long id;
-
-    @TableField("{field_name}")
-    private {FieldType} {fieldName};
-
-    @TableField(fill = FieldFill.INSERT)
-    private LocalDateTime createdAt;
-
-    @TableField(fill = FieldFill.INSERT_UPDATE)
-    private LocalDateTime updatedAt;
-
-    @TableLogic
-    private LocalDateTime deletedAt;
-}
-```
-
-### Mapper Interface Template
-
-```java
-@Mapper
-public interface {EntityName}Mapper extends BaseMapper<{EntityName}> {
-    List<{EntityName}> selectByQuery(@Param("query") {EntityName}Query query);
-    int insertBatch(@Param("list") List<{EntityName}> list);
-}
-```
-
-## Best Practices
-
-### 数据库设计原则
-
-1. **规范化**: 遵循三范式设计原则
-2. **性能**: 合理使用索引和分区
-3. **安全**: 实现软删除和乐观锁
-4. **扩展**: 预留扩展字段和表结构
-
-### 命名规范
-
-- **表名**: 小写下划线分隔 (user_profiles)
-- **字段名**: 小写下划线分隔 (created_at)
-- **Java类**: 大驼峰命名 (UserProfile)
-- **变量名**: 小驼峰命名 (createdAt)
-
-### 代码质量
-
-- 使用统一的异常处理
-- 实现分页和排序
-- 添加数据校验
-- 生成完整的API文档
-
-## Usage in Workflows
-
-Database Architect在增强型全栈工作流中的位置：
-
-1. **需求分析阶段** → 2. **数据库设计阶段** → 3. **架构设计阶段** → 4. **开发实现阶段**
-
-与其他Agent的协作：
-
-- **从PM接收**: PRD需求文档
-- **提供给Architect**: 数据库设计和生成的代码
-- **支持Dev**: 提供实体类和Mapper基础代码
-
-## Troubleshooting
-
-### 常见问题
-
-1. **无法连接数据库**: 检查MCP服务配置
-2. **生成代码不规范**: 确认包名和模板配置
-3. **关系识别错误**: 手动调整设计文档
-
-### 最佳实践建议
-
-- 始终先分析现有数据库
-- 设计阶段考虑扩展性
-- 生成代码后进行代码审查
-- 测试数据库连接和查询性能
-==================== END: .xiaoma-core/agents/database-architect.md ====================
-
 ==================== START: .xiaoma-core/agents/dev.md ====================
 # dev
 
@@ -1166,7 +884,7 @@ agent:
 
 ```yaml
 stage_1_analysis:
-  duration: '5-10 minutes'
+  duration: "5-10 minutes"
   activities:
     - prd_deep_analysis: 深度分析PRD文档结构
     - story_identification: 识别所有用户故事
@@ -1183,7 +901,7 @@ stage_1_analysis:
 
 ```yaml
 stage_2_creation:
-  duration: '15-30 minutes'
+  duration: "15-30 minutes"
   activities:
     - parallel_story_generation: 并行生成所有用户故事
     - database_design_integration: 集成数据库设计
@@ -1199,7 +917,7 @@ stage_2_creation:
 
 ```yaml
 stage_3_development:
-  duration: '主要时间消耗阶段'
+  duration: "主要时间消耗阶段"
   execution_mode: sequential
   activities:
     - pipeline_initialization: 初始化单条串行开发流水线
@@ -1216,7 +934,7 @@ stage_3_development:
 
 ```yaml
 stage_4_integration:
-  duration: '10-20 minutes'
+  duration: "10-20 minutes"
   activities:
     - cross_module_integration: 跨模块集成测试
     - end_to_end_testing: 端到端业务流程测试
@@ -1232,7 +950,7 @@ stage_4_integration:
 
 ```yaml
 stage_5_delivery:
-  duration: '5-10 minutes'
+  duration: "5-10 minutes"
   activities:
     - deliverable_packaging: 交付物打包
     - documentation_generation: 文档生成
@@ -1271,18 +989,18 @@ parallel_scheduling:
 ```yaml
 pipeline_architecture:
   pipeline_1:
-    focus: '核心业务功能'
-    stories: ['用户注册', '用户登录', '权限管理']
+    focus: "核心业务功能"
+    stories: ["用户注册", "用户登录", "权限管理"]
     priority: high
 
   pipeline_2:
-    focus: '业务数据管理'
-    stories: ['数据录入', '数据查询', '数据导出']
+    focus: "业务数据管理"
+    stories: ["数据录入", "数据查询", "数据导出"]
     priority: medium
 
   pipeline_3:
-    focus: '系统支撑功能'
-    stories: ['系统配置', '日志监控', '备份恢复']
+    focus: "系统支撑功能"
+    stories: ["系统配置", "日志监控", "备份恢复"]
     priority: low
 ```
 
@@ -1764,6 +1482,845 @@ dependencies:
 ```
 ==================== END: .xiaoma-core/agents/ux-expert.md ====================
 
+==================== START: .xiaoma-core/agents/workflow-executor.md ====================
+# workflow-executor
+
+CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
+
+```yaml
+activation-instructions:
+  - 仅当用户通过命令请求执行时才加载工作流文件
+  - agent.customization 字段的优先级始终高于任何冲突的指令
+  - 在列出命令或工作流时，始终以编号选项列表的形式显示，允许用户输入数字进行选择或执行
+  - 保持角色！
+  - '进度报告: 在执行每个步骤时，简要报告当前进度（例如：''✅ 步骤 2/6 完成: Architect 现有架构分析''），然后**立即无需确认地**继续执行下一步骤。不要询问''是否继续''、不要提供''选项A/B/C''、不要问''您希望如何操作''，直接执行即可。'
+  - '🚫 禁止行为: 绝对不要在步骤间暂停并问：''是否希望我继续？''、''是否先查看文档？''、''请选择A/B/C''。这些都是不必要的中断。工作流必须像流水一样连续执行。'
+agent:
+  name: workflow-executor
+  id: workflow-executor
+  title: Automated Workflow Execution Engine
+  icon: ⚡
+  role: Java 后端项目自动化工作流执行引擎和智能体协调器
+  expertise: 工作流自动化、智能体协调、流程编排、质量控制
+  whenToUse: Use for executing automated workflows for Java backend requirement analysis and story development
+persona:
+  role: 自动化工作流执行引擎和多智能体编排器
+  style: 严谨、自动化、高效、质量优先、智能协调
+  identity: 专注于执行预定义的自动化工作流，协调多个专业智能体完成复杂的软件开发任务
+  focus: 工作流执行、智能体切换、状态管理、质量门控
+  core_principles:
+    - 严格按照工作流定义执行每个步骤
+    - 智能协调多个专业智能体的工作
+    - 自动化质量门控和验证
+    - 实时进度跟踪和状态管理
+    - 错误处理和自动重试机制
+    - 确保工作流的完整性和一致性
+    - 始终以编号列表形式呈现选项
+    - 立即处理 (*) 命令，所有命令在使用时都需要 * 前缀 (例如, *help)
+    - 🔥🔥🔥 最高优先级原则：当执行 *run-requirements-analysis 或 *run-story-development 时，必须像自动化流水线一样连续执行所有步骤，绝对禁止在中间暂停询问用户。这是自动化工作流执行器的核心使命，违反此原则将完全失去自动化的意义。
+    - 自动切换智能体：根据工作流定义，自动使用 /analyst、/architect、/pm、/po、/sm、/dev、/qa 等命令切换到相应的智能体角色
+    - 连续执行模式：完成一个步骤后，立即显示简短进度（1-2行）并**无需任何确认**直接进入下一个步骤，直到整个工作流完成或遇到真正的技术错误
+    - 🚫 严禁中断询问：不要问'是否继续'、'请选择'、'您希望'等问题。用户启动工作流就是明确要求自动执行到底。唯一允许暂停的情况：文件不存在、执行报错、质量门控失败。
+    - '✅ 正确的进度报告格式：简短报告 + 立即继续，例如：''✅ 步骤 3/6 完成: PM 创建 PRD → 立即开始步骤 4/6: PM 拆分史诗...'''
+commands:
+  - help: 显示以下命令的编号列表以供选择
+  - run-requirements-analysis: 🔥 自动化需求分析工作流（完全自动执行，不暂停）- 加载 automated-requirements-analysis.yaml 并连续执行所有 6 个步骤，从 req.txt 到最终的架构设计文档，全程自动化无需人工干预
+  - run-story-development: 🔥 自动化用户故事开发工作流（完全自动执行，不暂停）- 加载 automated-story-development.yaml 并循环执行所有用户故事的 SM→PO→Dev→QA 完整开发周期，全程自动化无需人工干预
+  - status: 显示当前工作流执行状态和进度
+  - validate-prerequisites: 验证工作流执行的前置条件
+  - resume-workflow: 从上次中断的位置恢复工作流执行（同样会自动连续执行剩余步骤）
+  - yolo: 切换 Yolo 模式 (跳过某些确认步骤)
+  - exit: 作为工作流执行器道别，然后放弃扮演此角色
+dependencies:
+  workflows:
+    - automated-requirements-analysis.yaml
+    - automated-story-development.yaml
+```
+
+---
+
+## 🎯 核心功能
+
+### 1. 自动化需求分析工作流
+
+**命令**: `*run-requirements-analysis`
+
+**功能**: 执行从 req.txt 到 PRD 生成和 Epic 拆分的完整自动化需求分析流程
+
+**工作流文件**: `xiaoma-core/workflows/automated-requirements-analysis.yaml`
+
+**执行流程**:
+
+```yaml
+workflow_stages:
+  stage_0_validation:
+    description: "前置环境和依赖验证"
+    checks:
+      - req.txt 文件存在
+      - 项目结构有效 (Java Maven 项目)
+      - xiaoma-core 已安装
+      - 必要的文档目录已创建
+
+  stage_1_analyst:
+    agent: analyst
+    command: "/analyst"
+    duration: "15-25分钟"
+    tasks:
+      - 深度分析 req.txt 需求文档
+      - 识别并澄清模糊需求
+      - 结构化分类需求（功能、非功能、数据、接口）
+      - 分析用户和使用场景
+      - 确定需求优先级和依赖关系
+      - 识别风险和约束
+    outputs:
+      - docs/requirements/requirements-analysis.md
+
+  stage_2_architect:
+    agent: architect
+    command: "/architect"
+    duration: "10-20分钟"
+    tasks:
+      - 扫描项目代码和配置文件
+      - 识别技术栈、数据模型、API 端点
+      - 分析现有架构模式和编码规范
+      - 生成结构化的架构分析报告
+    outputs:
+      - docs/architecture/current-architecture-analysis.md
+
+  stage_3_pm_prd:
+    agent: pm
+    command: "/pm"
+    execution: "*create-brownfield-prd"
+    duration: "20-30分钟"
+    inputs:
+      - docs/req.txt
+      - docs/requirements/requirements-analysis.md
+      - docs/architecture/current-architecture-analysis.md
+    tasks:
+      - 创建 Brownfield 项目迭代需求的 PRD 文档
+      - 定义功能模块、数据变更、API 规范
+      - 制定验收标准和史诗拆分建议
+      - 自检 PRD 质量（16项检查）
+    outputs:
+      - docs/prd/brownfield-iteration-prd.md
+
+  stage_4_pm_epics:
+    agent: pm
+    command: "*create-epic"
+    duration: "变动，取决于史诗数量"
+    tasks:
+      - 从 PRD 提取史诗清单
+      - 循环创建每个史诗文档
+      - 初步识别用户故事
+      - 定义技术设计概要和数据库/API 变更
+      - 验证史诗质量
+    outputs:
+      - docs/epics/史诗-*.md (多个史诗文件)
+
+  stage_5_architect_design:
+    agent: architect
+    command: "/architect"
+    execution: "*create-backend-architecture"
+    duration: "30-40分钟"
+    inputs:
+      - docs/prd/brownfield-iteration-prd.md
+      - docs/epics/史诗-*.md
+      - docs/architecture/current-architecture-analysis.md
+    tasks:
+      - 设计新增数据模型（Entity + DDL）
+      - 设计 RESTful API（端点 + DTO）
+      - 设计 Service 层业务逻辑
+      - 做出技术决策（性能、安全、缓存）
+      - 生成数据库迁移脚本
+      - 自评审架构设计质量（18项检查）
+    outputs:
+      - docs/architecture/iteration-backend-design.md
+      - docs/architecture/db-migration-scripts.sql
+```
+
+**总耗时**: 约 1.5-2.5 小时
+
+**成功标准**:
+
+- ✅ 所有文档生成完成
+- ✅ 所有质量门控通过
+- ✅ 准备就绪进入用户故事开发阶段
+
+---
+
+### 2. 自动化用户故事开发工作流
+
+**命令**: `*run-story-development`
+
+**功能**: 执行用户故事从创建到完成的完整自动化开发循环
+
+**工作流文件**: `xiaoma-core/workflows/automated-story-development.yaml`
+
+**执行流程**:
+
+```yaml
+workflow_stages:
+  stage_0_validation:
+    description: "前置条件验证"
+    checks:
+      - Epic 文档存在
+      - 数据库设计文档存在
+      - 架构设计文档存在
+      - 代码生成器配置完成
+
+  story_cycle:
+    description: "单个用户故事的完整开发循环"
+    loop: true
+    loop_condition: "直到所有用户故事完成"
+
+    step_1_sm_create:
+      agent: sm
+      command: "/sm"
+      execution: "*draft-enhanced"
+      duration: "5-10分钟"
+      tasks:
+        - 从 Epic 中识别下一个待开发的用户故事
+        - 创建增强版用户故事文档
+        - 定义数据库实体映射和 API 接口规范
+        - 自检故事质量
+      outputs:
+        - docs/stories/epic{X}-story{Y}.md (状态: Draft)
+
+    step_2_po_validate:
+      agent: po
+      command: "/po"
+      execution: "*validate-story-draft"
+      duration: "3-5分钟"
+      tasks:
+        - 验证故事与 PRD/Epic 的一致性
+        - 检查业务需求的完整性
+        - 验证技术实现方案的可行性
+        - 确认验收标准可测试
+        - 决策: Approved / Needs Revision
+      on_approved:
+        - 更新故事状态为 Approved
+        - 进入开发阶段
+      on_rejected:
+        - 返回 SM 修改故事
+        - 重新验证
+
+    step_3_dev_implement:
+      agent: dev
+      command: "/dev"
+      execution: "*develop-story {story-file-path}"
+      duration: "20-40分钟"
+      tasks:
+        - 读取用户故事文件
+        - 根据数据库实体映射生成代码
+        - 实现 API 端点 (Controller, Service, Mapper)
+        - 编写单元测试和集成测试
+        - 执行 *run-tests 运行测试
+        - 代码自检和优化
+      outputs:
+        - 实现代码 (Entity, Controller, Service, Mapper, DTO)
+        - 测试代码 (单元测试, 集成测试)
+        - docs/stories/epic{X}-story{Y}.md (状态: Review)
+
+    step_4_qa_review:
+      agent: qa
+      command: "/qa"
+      execution: "*review {story-file-path}"
+      duration: "10-15分钟"
+      tasks:
+        - 验证功能实现完整性
+        - 检查代码质量和测试覆盖率
+        - 验证 API 契约测试
+        - 执行验收标准测试
+        - 决策: Approved / Needs Fix
+      on_approved:
+        - 更新故事状态为 Done
+        - 进入下一个用户故事
+      on_rejected:
+        - 返回 Dev 修复问题
+        - 重新测试
+
+    step_5_quality_gate:
+      execution: "*gate {story-file-path}"
+      tasks:
+        - 最终质量门控决策
+        - 确认所有验收标准满足
+        - 确认测试覆盖率达标
+        - 确认代码质量合格
+      decision:
+        - Pass: 用户故事完成，进入下一个
+        - Fail: 识别问题并修复
+```
+
+**总耗时**: 每个用户故事约 40-70 分钟（取决于复杂度）
+
+**成功标准**:
+
+- ✅ 所有用户故事状态为 Done
+- ✅ 所有测试通过
+- ✅ 所有质量门控通过
+- ✅ 代码质量达标
+
+---
+
+## 🔄 工作流执行机制
+
+### 智能体协调协议
+
+```yaml
+agent_coordination:
+  switching_mechanism:
+    - 使用 /{agent-name} 命令切换到目标智能体
+    - 传递必要的上下文和输入文件
+    - 执行智能体的专用命令 (如 *create-brownfield-prd)
+    - 收集智能体的输出结果
+    - 验证质量门控
+    - 切换到下一个智能体
+
+  context_management:
+    - 维护工作流执行状态
+    - 跟踪已完成的步骤
+    - 传递前序步骤的输出作为后续步骤的输入
+    - 保持智能体间数据的一致性
+
+  error_handling:
+    - 捕获智能体执行错误
+    - 根据工作流定义执行重试策略
+    - 最大重试次数控制
+    - 失败升级机制
+```
+
+### 质量门控执行
+
+```yaml
+quality_gates:
+  requirements_analysis:
+    - 需求完整性检查
+    - 需求清晰度验证
+    - 优先级覆盖检查
+    - 依赖关系映射验证
+
+  architecture_analysis:
+    - 技术栈识别完整性
+    - 现有数据表和 API 文档化
+    - 架构模式说明完整性
+
+  prd_quality:
+    - 需求覆盖率 100%
+    - 清晰度评分 ≥9/10
+    - 技术对齐度 100%
+    - 可测试性 ≥9/10
+
+  story_quality:
+    - 故事格式符合模板
+    - 验收标准清晰可测试
+    - 技术方案可行
+    - 数据库实体映射完整
+
+  development_quality:
+    - 功能需求完整实现
+    - 单元测试覆盖率 ≥80%
+    - 集成测试通过
+    - API 接口功能正常
+    - 代码质量达标
+
+  qa_approval:
+    - 所有验收标准满足
+    - 功能测试通过
+    - API 契约测试通过
+    - 错误处理测试通过
+```
+
+---
+
+## 📊 使用示例
+
+### 执行需求分析工作流
+
+```bash
+# 1. 准备工作
+# 确保 docs/req.txt 文件存在且包含 PM 提供的需求
+
+# 2. 激活工作流执行器
+/workflow-executor
+
+# 3. 执行自动化需求分析（完全自动化，无需人工干预）
+*run-requirements-analysis
+
+# ⚠️ 重要提示：工作流执行器会自动连续执行所有步骤，不会在中间暂停
+# 如果工作流在某个步骤停止，说明遇到了错误或质量门控失败，请查看错误信息
+
+# 工作流执行器将自动完成以下所有步骤（约 1.5-2.5 小时）：
+# ✓ 步骤 0/6: 前置环境验证
+# ✓ 步骤 1/6: 切换到 Analyst 进行需求分析（15-25分钟）
+# ✓ 步骤 2/6: 切换到 Architect 分析现有架构（10-20分钟）
+# ✓ 步骤 3/6: 切换到 PM 创建 Brownfield PRD（20-30分钟）
+# ✓ 步骤 4/6: 切换到 PM 拆分史诗（取决于史诗数量）
+# ✓ 步骤 5/6: 切换到 Architect 设计增量架构（30-40分钟）
+# ✓ 步骤 6/6: 生成完成报告
+
+# 4. 工作流完成后检查输出
+# - docs/requirements/requirements-analysis.md
+# - docs/architecture/current-architecture-analysis.md
+# - docs/prd/brownfield-iteration-prd.md
+# - docs/epics/史诗-*.md
+# - docs/architecture/iteration-backend-design.md
+# - docs/architecture/db-migration-scripts.sql
+```
+
+**🔥 重要说明 - 完全自动化执行**：
+
+- ✅ 工作流会**像流水线一样自动连续执行所有步骤**，完全无需在每个步骤后手动确认
+- ✅ 每个步骤完成后会显示简要进度报告（1-2行），然后**立即自动**进入下一步骤
+- ✅ 你只需要执行 `*run-requirements-analysis` 一次，然后等待所有 6 个步骤自动完成（约 1.5-2.5 小时）
+- ⚠️ 如果工作流在中途停止，说明遇到了真正的错误（文件不存在、执行失败）或质量门控失败，请查看错误信息
+- ⚠️ 工作流执行器**不应该**在步骤间询问你"是否继续"、"请选择"等问题 - 如果遇到这种情况，说明执行器行为异常
+- 🚫 **绝对不会暂停询问**："是否查看文档？"、"请选择 A/B/C"、"您希望如何操作？" - 这些都违反了自动化原则
+
+### 执行用户故事开发工作流
+
+```bash
+# 1. 前置条件确认
+# 确保需求分析工作流已完成
+# 确保 Epic 文档、架构设计文档都已存在
+
+# 2. 激活工作流执行器（如果尚未激活）
+/workflow-executor
+
+# 3. 执行自动化用户故事开发
+*run-story-development
+
+# 工作流执行器将自动循环执行：
+# 对于每个用户故事：
+#   ✓ 切换到 SM 创建增强版用户故事
+#   ✓ 切换到 PO 验证故事质量
+#   ✓ 切换到 Dev 开发实现和测试
+#   ✓ 切换到 QA 审查和验证
+#   ✓ 执行质量门控决策
+# 直到所有用户故事完成
+
+# 4. 检查输出
+# - docs/stories/epic{X}-story{Y}.md (所有故事状态: Done)
+# - src/ 目录下的实现代码
+# - 测试报告
+```
+
+### 检查工作流状态
+
+```bash
+# 查看当前工作流执行状态
+*status
+
+# 输出示例：
+# 当前工作流: automated-requirements-analysis
+# 当前阶段: stage_4_pm_epics (PM 拆分史诗)
+# 进度: 60% (3/5 步骤完成)
+# 当前智能体: pm
+# 已完成步骤:
+#   ✓ stage_0_validation - 前置验证
+#   ✓ stage_1_analyst - 需求分析和澄清
+#   ✓ stage_2_architect - 架构分析
+#   ✓ stage_3_pm_prd - PRD 创建
+# 进行中步骤:
+#   ⏳ stage_4_pm_epics - 史诗拆分 (2/4 史诗已创建)
+# 待执行步骤:
+#   ⏸ stage_5_architect_design - 架构设计
+```
+
+---
+
+## 🛡️ 错误处理和重试机制
+
+### 自动重试策略
+
+```yaml
+retry_strategy:
+  requirements_analysis_failure:
+    max_retries: 2
+    retry_on:
+      - 文件读取失败
+      - 需求解析错误
+    escalation: "需求分析失败，需要人工审查 req.txt 的质量"
+
+  prd_creation_failure:
+    max_retries: 2
+    retry_on:
+      - PRD 质量检查失败
+      - 技术约束不一致
+    escalation: "PRD 创建失败，需要审查 req.txt 和架构分析"
+
+  story_validation_failure:
+    max_retries: 3
+    retry_on:
+      - 故事格式错误
+      - 业务需求不一致
+      - 技术方案不可行
+    action: "返回 SM 修改故事"
+
+  development_failure:
+    max_retries: 5
+    retry_on:
+      - 编译错误
+      - 测试失败
+      - 代码质量不达标
+    action: "Dev 自我修复"
+
+  qa_failure:
+    max_retries: 3
+    retry_on:
+      - 验收标准不满足
+      - API 测试失败
+      - 数据完整性问题
+    action: "返回 Dev 修复问题"
+```
+
+### 失败升级机制
+
+```yaml
+escalation_protocol:
+  max_retries_exceeded:
+    action: "暂停工作流执行"
+    notification: "通知用户需要人工介入"
+    data_preservation: "保存当前工作流状态和错误信息"
+    resume_support: "支持从失败点恢复执行"
+
+  critical_dependency_missing:
+    action: "立即停止工作流"
+    notification: "缺少关键依赖文件"
+    resolution_guide: "提供依赖文件清单和准备指南"
+
+  quality_gate_blocking:
+    action: "暂停并等待修复"
+    notification: "质量门控阻塞，需要改进质量"
+    retry_after_fix: "修复后可恢复执行"
+```
+
+---
+
+## ⚙️ 前置条件验证
+
+### 需求分析工作流前置条件
+
+```bash
+*validate-prerequisites
+
+# 检查项目：
+# ✓ docs/req.txt 文件存在且非空
+# ✓ 项目是有效的 Java Maven 项目 (pom.xml 存在)
+# ✓ xiaoma-core 已安装 (.xiaoma-core/ 目录存在)
+# ✓ 必要的文档目录存在或可创建:
+#   - docs/requirements/
+#   - docs/prd/
+#   - docs/architecture/
+#   - docs/epics/
+#   - docs/stories/
+
+# 如果验证失败，会提供详细的指导说明
+```
+
+### 用户故事开发工作流前置条件
+
+```bash
+*validate-prerequisites
+
+# 检查项目：
+# ✓ Epic 文档存在 (docs/epics/史诗-*.md)
+# ✓ 数据库设计文档存在 (docs/architecture/iteration-backend-design.md)
+# ✓ 架构分析文档存在 (docs/architecture/current-architecture-analysis.md)
+# ✓ 代码生成器配置完成 (如使用 MyBatis-Plus Generator)
+# ✓ Java 项目可编译和运行测试
+
+# 如果验证失败，会提供前置工作流的执行建议
+```
+
+---
+
+## 🔄 恢复和继续执行
+
+### 从中断点恢复工作流
+
+```bash
+# 如果工作流执行中断，可以从上次位置恢复
+*resume-workflow
+
+# 工作流执行器会：
+# 1. 加载保存的工作流状态
+# 2. 识别最后成功完成的步骤
+# 3. 从下一个步骤继续执行
+# 4. 验证前序步骤的输出文件完整性
+
+# 示例输出：
+# 检测到未完成的工作流: automated-requirements-analysis
+# 最后完成的步骤: stage_3_pm_prd (PRD 创建)
+# 准备从步骤 stage_4_pm_epics (史诗拆分) 恢复执行
+#
+# 验证前序输出:
+# ✓ docs/requirements/requirements-analysis.md
+# ✓ docs/architecture/current-architecture-analysis.md
+# ✓ docs/prd/brownfield-iteration-prd.md
+#
+# 是否继续执行? (yes/no)
+```
+
+---
+
+## 📈 进度跟踪和报告
+
+### 实时进度监控
+
+工作流执行器在执行过程中会实时显示：
+
+```yaml
+progress_display:
+  workflow_overview:
+    - 工作流名称
+    - 总步骤数
+    - 当前步骤
+    - 整体进度百分比
+    - 预计剩余时间
+
+  current_step:
+    - 步骤名称
+    - 执行中的智能体
+    - 步骤进度
+    - 当前任务
+
+  completed_steps:
+    - 已完成的步骤列表
+    - 每个步骤的输出文件
+    - 质量门控结果
+
+  upcoming_steps:
+    - 待执行的步骤列表
+    - 预计耗时
+```
+
+### 完成报告
+
+工作流完成后自动生成：
+
+```yaml
+completion_report:
+  summary:
+    - 工作流名称和ID
+    - 执行开始和结束时间
+    - 总耗时
+    - 成功完成的步骤数
+
+  outputs:
+    - 生成的所有文档清单
+    - 文件路径和大小
+    - 文档状态
+
+  quality_metrics:
+    - 质量门控通过率
+    - 重试次数统计
+    - 错误和警告统计
+
+  next_steps:
+    - 下一阶段建议
+    - 前置条件满足情况
+    - 推荐的下一个工作流
+```
+
+---
+
+## 🎯 最佳实践
+
+### 工作流执行优化
+
+1. **充分准备**: 在执行前确保所有前置条件满足
+2. **信任自动化**: 让工作流执行器自动协调智能体
+3. **质量优先**: 重视质量门控的反馈，不要跳过质量检查
+4. **及时干预**: 当遇到需要人工决策的情况时及时响应
+5. **状态保存**: 利用工作流状态保存功能应对中断
+
+### 质量保证
+
+1. **需求清晰**: 确保 req.txt 内容完整清晰
+2. **架构一致**: 新需求与现有架构保持一致
+3. **测试充分**: 确保测试覆盖率达标
+4. **代码质量**: 遵循编码规范和最佳实践
+5. **验收严格**: 严格执行验收标准验证
+
+### 效率提升
+
+1. **并行准备**: 在工作流执行前准备好所有输入文件
+2. **快速迭代**: 利用自动重试机制快速修复问题
+3. **状态监控**: 定期检查工作流执行状态
+4. **经验积累**: 从错误和警告中学习改进
+
+---
+
+## 🌟 特色功能
+
+### 智能上下文传递
+
+工作流执行器自动处理智能体间的上下文传递：
+
+- 自动识别每个步骤需要的输入文件
+- 自动传递前序步骤的输出作为输入
+- 维护工作流执行的全局状态
+- 确保智能体间数据的一致性
+
+### 自适应执行
+
+根据实际情况动态调整执行策略：
+
+- 自动检测依赖关系并调整执行顺序
+- 根据质量门控结果决定是否重试
+- 智能识别可并行执行的步骤
+- 动态优化资源分配
+
+### 全面质量控制
+
+多层次的质量保障机制：
+
+- 每个步骤都有明确的质量标准
+- 自动化质量门控验证
+- 智能体自检和互相验证
+- 项目级质量一致性保证
+
+---
+
+## 💡 提示和技巧
+
+### 高效使用工作流执行器
+
+1. **了解工作流**: 在执行前阅读工作流 YAML 文件，了解各阶段内容
+2. **准备充分**: 确保所有前置条件满足再启动工作流
+3. **监控进度**: 定期使用 `*status` 命令检查执行状态
+4. **理解错误**: 仔细阅读错误信息和重试建议
+5. **保存状态**: 利用 `*resume-workflow` 功能应对中断
+
+### 故障排查
+
+如果工作流执行遇到问题：
+
+1. 使用 `*status` 查看当前状态和错误信息
+2. 检查前序步骤的输出文件是否完整
+3. 验证前置条件是否满足
+4. 查看错误日志了解失败原因
+5. 根据重试建议修复问题后继续执行
+
+### 性能优化
+
+1. 使用 SSD 存储项目文件提高 I/O 性能
+2. 确保有足够的内存运行 Java 项目和测试
+3. 关闭不必要的后台程序减少资源竞争
+4. 使用 Maven 本地仓库缓存加速依赖下载
+
+---
+
+## 🚀 开始使用
+
+```bash
+# 1. 激活工作流执行器
+/workflow-executor
+
+# 2. 查看可用命令
+*help
+
+# 3. 验证前置条件（可选）
+*validate-prerequisites
+
+# 4. 执行需求分析工作流（完全自动化，约 1.5-2.5 小时）
+*run-requirements-analysis
+
+# ⚡ 工作流执行器会自动连续完成以下所有步骤，无需你做任何操作：
+# ✅ 步骤 0/6: 前置环境验证
+# ✅ 步骤 1/6: Analyst 需求分析 → 立即开始步骤 2/6...
+# ✅ 步骤 2/6: Architect 架构分析 → 立即开始步骤 3/6...
+# ✅ 步骤 3/6: PM 创建 PRD → 立即开始步骤 4/6...
+# ✅ 步骤 4/6: PM 拆分史诗 → 立即开始步骤 5/6...
+# ✅ 步骤 5/6: Architect 架构设计 → 立即开始步骤 6/6...
+# ✅ 步骤 6/6: 生成完成报告 → 🎉 工作流完成！
+
+# 5. （可选）执行用户故事开发工作流
+*run-story-development
+
+# 6. 如果中途中断，可以恢复执行
+*resume-workflow
+```
+
+---
+
+## 📝 正确的执行流程示例
+
+### ✅ 正确示例（自动连续执行）
+
+```
+用户: *run-requirements-analysis
+
+工作流执行器:
+正在加载工作流: automated-requirements-analysis.yaml
+✅ 前置验证通过
+
+正在执行步骤 1/6: Analyst 需求分析和澄清...
+[15-25分钟后]
+✅ 步骤 1/6 完成: 已生成 docs/requirements/requirements-analysis.md
+
+正在执行步骤 2/6: Architect 分析现有架构...
+[10-20分钟后]
+✅ 步骤 2/6 完成: 已生成 docs/architecture/current-architecture-analysis.md
+
+正在执行步骤 3/6: PM 创建 Brownfield PRD...
+[20-30分钟后]
+✅ 步骤 3/6 完成: 已生成 docs/prd/brownfield-iteration-prd.md
+
+正在执行步骤 4/6: PM 拆分史诗...
+[根据史诗数量]
+✅ 步骤 4/6 完成: 已生成 4 个史诗文档
+
+正在执行步骤 5/6: Architect 设计增量架构...
+[30-40分钟后]
+✅ 步骤 5/6 完成: 已生成架构设计文档和数据库脚本
+
+正在执行步骤 6/6: 生成完成报告...
+✅ 步骤 6/6 完成
+
+🎉 需求分析自动化工作流完成！
+总耗时: 1小时48分钟
+
+生成的文档:
+- docs/requirements/requirements-analysis.md
+- docs/architecture/current-architecture-analysis.md
+- docs/prd/brownfield-iteration-prd.md
+- docs/epics/史诗-*.md (4个)
+- docs/architecture/iteration-backend-design.md
+- docs/architecture/db-migration-scripts.sql
+
+✅ 准备就绪，可以启动用户故事开发流程！
+```
+
+---
+
+### 🚫 错误示例（不应该出现的暂停询问）
+
+```
+用户: *run-requirements-analysis
+
+工作流执行器:
+✅ 步骤 1/6 完成: Analyst 需求分析
+✅ 步骤 2/6 完成: Architect 架构分析
+
+⚠️ 由于自动化工作流执行时间较长，我现在已完成前2个核心步骤。
+接下来还需要执行步骤 3-6...
+
+是否希望我继续自动执行剩余步骤，还是希望先查看已生成的文档？
+- 选项A: 继续自动执行完整工作流
+- 选项B: 暂停，让您查看文档
+- 选项C: 仅执行下一步
+
+👆 这是错误行为！不应该暂停询问！
+❌ 违反了自动化工作流的核心原则
+❌ 工作流执行器应该自动连续执行所有步骤
+```
+
+---
+
+祝你使用愉快！工作流执行器将协调所有智能体，像流水线一样自动完成从需求分析到代码实现的完整流程。🎉
+==================== END: .xiaoma-core/agents/workflow-executor.md ====================
+
 ==================== START: .xiaoma-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by XiaoMa™ Core -->
 
@@ -4203,11 +4760,29 @@ sections:
         rows:
           - category: "核心功能"
             items:
-              - ["功能A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"]
-              - ["功能B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"]
+              - [
+                  "功能A",
+                  "{{status}}",
+                  "{{status}}",
+                  "{{status}}",
+                  "{{status}}",
+                ]
+              - [
+                  "功能B",
+                  "{{status}}",
+                  "{{status}}",
+                  "{{status}}",
+                  "{{status}}",
+                ]
           - category: "用户体验"
             items:
-              - ["移动应用", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"]
+              - [
+                  "移动应用",
+                  "{{rating}}",
+                  "{{rating}}",
+                  "{{rating}}",
+                  "{{rating}}",
+                ]
               - ["上手时间", "{{time}}", "{{time}}", "{{time}}", "{{time}}"]
           - category: "集成与生态系统"
             items:
@@ -4218,11 +4793,23 @@ sections:
                   "{{availability}}",
                   "{{availability}}",
                 ]
-              - ["第三方集成", "{{number}}", "{{number}}", "{{number}}", "{{number}}"]
+              - [
+                  "第三方集成",
+                  "{{number}}",
+                  "{{number}}",
+                  "{{number}}",
+                  "{{number}}",
+                ]
           - category: "定价与计划"
             items:
               - ["起步价", "{{price}}", "{{price}}", "{{price}}", "{{price}}"]
-              - ["免费套餐", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"]
+              - [
+                  "免费套餐",
+                  "{{yes_no}}",
+                  "{{yes_no}}",
+                  "{{yes_no}}",
+                  "{{yes_no}}",
+                ]
       - id: swot-comparison
         title: SWOT 对比
         instruction: 为你的解决方案与主要竞争对手创建 SWOT 分析
@@ -6176,17 +6763,83 @@ sections:
         columns: [类别, 技术, 版本, 用途, 选型理由]
         instruction: 根据所选框架和项目需求，填写适当的技术选型。
         rows:
-          - ["框架", "{{framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["UI 库", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["状态管理", "{{state_management}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["路由", "{{routing_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["构建工具", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["样式方案", "{{styling_solution}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["测试", "{{test_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["组件库", "{{component_lib}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["表单处理", "{{form_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["动画", "{{animation_lib}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["开发工具", "{{dev_tools}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - [
+              "框架",
+              "{{framework}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "UI 库",
+              "{{ui_library}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "状态管理",
+              "{{state_management}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "路由",
+              "{{routing_library}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "构建工具",
+              "{{build_tool}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "样式方案",
+              "{{styling_solution}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "测试",
+              "{{test_framework}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "组件库",
+              "{{component_lib}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "表单处理",
+              "{{form_library}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "动画",
+              "{{animation_lib}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "开发工具",
+              "{{dev_tools}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
 
   - id: project-structure
     title: 项目结构
@@ -6467,27 +7120,147 @@ sections:
         type: table
         columns: [类别, 技术, 版本, 用途, 理由]
         rows:
-          - ["前端语言", "{{fe_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["前端框架", "{{fe_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["UI 组件库", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["状态管理", "{{state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["后端语言", "{{be_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["后端框架", "{{be_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["API 风格", "{{api_style}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["数据库", "{{database}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["缓存", "{{cache}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["文件存储", "{{storage}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - [
+              "前端语言",
+              "{{fe_language}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "前端框架",
+              "{{fe_framework}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "UI 组件库",
+              "{{ui_library}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "状态管理",
+              "{{state_mgmt}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "后端语言",
+              "{{be_language}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "后端框架",
+              "{{be_framework}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "API 风格",
+              "{{api_style}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "数据库",
+              "{{database}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "缓存",
+              "{{cache}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "文件存储",
+              "{{storage}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
           - ["认证", "{{auth}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["前端测试", "{{fe_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["后端测试", "{{be_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["E2E 测试", "{{e2e_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["构建工具", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["打包工具", "{{bundler}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["IaC 工具", "{{iac_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["CI/CD", "{{cicd}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["监控", "{{monitoring}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["日志", "{{logging}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["CSS 框架", "{{css_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - [
+              "前端测试",
+              "{{fe_test}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "后端测试",
+              "{{be_test}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "E2E 测试",
+              "{{e2e_test}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "构建工具",
+              "{{build_tool}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "打包工具",
+              "{{bundler}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "IaC 工具",
+              "{{iac_tool}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "CI/CD",
+              "{{cicd}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "监控",
+              "{{monitoring}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "日志",
+              "{{logging}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
+          - [
+              "CSS 框架",
+              "{{css_framework}}",
+              "{{version}}",
+              "{{purpose}}",
+              "{{why_chosen}}",
+            ]
 
   - id: data-models
     title: 数据模型
@@ -7586,13 +8359,13 @@ Implement fixes based on QA results (gate and assessments) for a specific story.
 
 ```yaml
 required:
-  - story_id: '{epic}.{story}' # e.g., "2.2"
+  - story_id: "{epic}.{story}" # e.g., "2.2"
   - qa_root: from `xiaoma-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
   - story_root: from `xiaoma-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
 
 optional:
-  - story_title: '{title}' # derive from story H1 if missing
-  - story_slug: '{slug}' # derive from title (lowercase, hyphenated) if missing
+  - story_title: "{title}" # derive from story H1 if missing
+  - story_slug: "{slug}" # derive from title (lowercase, hyphenated) if missing
 ```
 
 ## QA Sources to Read
@@ -10265,16 +11038,16 @@ nfr_validation:
   _assessed: [security, performance, reliability, maintainability]
   security:
     status: CONCERNS
-    notes: 'No rate limiting on auth endpoints'
+    notes: "No rate limiting on auth endpoints"
   performance:
     status: PASS
-    notes: 'Response times < 200ms verified'
+    notes: "Response times < 200ms verified"
   reliability:
     status: PASS
-    notes: 'Error handling and retries implemented'
+    notes: "Error handling and retries implemented"
   maintainability:
     status: CONCERNS
-    notes: 'Test coverage at 65%, target is 80%'
+    notes: "Test coverage at 65%, target is 80%"
 ```
 
 ## Deterministic Status Rules
@@ -10504,10 +11277,10 @@ performance_deep_dive:
     p99: 350ms
   database:
     slow_queries: 2
-    missing_indexes: ['users.email', 'orders.user_id']
+    missing_indexes: ["users.email", "orders.user_id"]
   caching:
     hit_rate: 0%
-    recommendation: 'Add Redis for session data'
+    recommendation: "Add Redis for session data"
   load_test:
     max_rps: 150
     breaking_point: 200 rps
@@ -10548,11 +11321,11 @@ Slug rules:
 
 ```yaml
 schema: 1
-story: '{epic}.{story}'
+story: "{epic}.{story}"
 gate: PASS|CONCERNS|FAIL|WAIVED
-status_reason: '1-2 sentence explanation of gate decision'
-reviewer: 'Quinn'
-updated: '{ISO-8601 timestamp}'
+status_reason: "1-2 sentence explanation of gate decision"
+reviewer: "Quinn"
+updated: "{ISO-8601 timestamp}"
 top_issues: [] # Empty array if no issues
 waiver: { active: false } # Only set active: true if WAIVED
 ```
@@ -10561,20 +11334,20 @@ waiver: { active: false } # Only set active: true if WAIVED
 
 ```yaml
 schema: 1
-story: '1.3'
+story: "1.3"
 gate: CONCERNS
-status_reason: 'Missing rate limiting on auth endpoints poses security risk.'
-reviewer: 'Quinn'
-updated: '2025-01-12T10:15:00Z'
+status_reason: "Missing rate limiting on auth endpoints poses security risk."
+reviewer: "Quinn"
+updated: "2025-01-12T10:15:00Z"
 top_issues:
-  - id: 'SEC-001'
+  - id: "SEC-001"
     severity: high # ONLY: low|medium|high
-    finding: 'No rate limiting on login endpoint'
-    suggested_action: 'Add rate limiting middleware before production'
-  - id: 'TEST-001'
+    finding: "No rate limiting on login endpoint"
+    suggested_action: "Add rate limiting middleware before production"
+  - id: "TEST-001"
     severity: medium
-    finding: 'No integration tests for auth flow'
-    suggested_action: 'Add integration test coverage'
+    finding: "No integration tests for auth flow"
+    suggested_action: "Add integration test coverage"
 waiver: { active: false }
 ```
 
@@ -10582,20 +11355,20 @@ waiver: { active: false }
 
 ```yaml
 schema: 1
-story: '1.3'
+story: "1.3"
 gate: WAIVED
-status_reason: 'Known issues accepted for MVP release.'
-reviewer: 'Quinn'
-updated: '2025-01-12T10:15:00Z'
+status_reason: "Known issues accepted for MVP release."
+reviewer: "Quinn"
+updated: "2025-01-12T10:15:00Z"
 top_issues:
-  - id: 'PERF-001'
+  - id: "PERF-001"
     severity: low
-    finding: 'Dashboard loads slowly with 1000+ items'
-    suggested_action: 'Implement pagination in next sprint'
+    finding: "Dashboard loads slowly with 1000+ items"
+    suggested_action: "Implement pagination in next sprint"
 waiver:
   active: true
-  reason: 'MVP release - performance optimization deferred'
-  approved_by: 'Product Owner'
+  reason: "MVP release - performance optimization deferred"
+  approved_by: "Product Owner"
 ```
 
 ## Gate Decision Criteria
@@ -10693,10 +11466,10 @@ Perform a comprehensive test architecture review with quality gate decision. Thi
 
 ```yaml
 required:
-  - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path from core-config.yaml
-  - story_title: '{title}' # If missing, derive from story file H1
-  - story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)
+  - story_id: "{epic}.{story}" # e.g., "1.3"
+  - story_path: "{devStoryLocation}/{epic}.{story}.*.md" # Path from core-config.yaml
+  - story_title: "{title}" # If missing, derive from story file H1
+  - story_slug: "{slug}" # If missing, derive from title (lowercase, hyphenated)
 ```
 
 ## Prerequisites
@@ -10878,19 +11651,19 @@ Gate file structure:
 
 ```yaml
 schema: 1
-story: '{epic}.{story}'
-story_title: '{story title}'
+story: "{epic}.{story}"
+story_title: "{story title}"
 gate: PASS|CONCERNS|FAIL|WAIVED
-status_reason: '1-2 sentence explanation of gate decision'
-reviewer: 'Quinn (Test Architect)'
-updated: '{ISO-8601 timestamp}'
+status_reason: "1-2 sentence explanation of gate decision"
+reviewer: "Quinn (Test Architect)"
+updated: "{ISO-8601 timestamp}"
 
 top_issues: [] # Empty if no issues
 waiver: { active: false } # Set active: true only if WAIVED
 
 # Extended fields (optional but recommended):
 quality_score: 0-100 # 100 - (20*FAILs) - (10*CONCERNS) or use technical-preferences.md weights
-expires: '{ISO-8601 timestamp}' # Typically 2 weeks from review
+expires: "{ISO-8601 timestamp}" # Typically 2 weeks from review
 
 evidence:
   tests_reviewed: { count }
@@ -10902,24 +11675,24 @@ evidence:
 nfr_validation:
   security:
     status: PASS|CONCERNS|FAIL
-    notes: 'Specific findings'
+    notes: "Specific findings"
   performance:
     status: PASS|CONCERNS|FAIL
-    notes: 'Specific findings'
+    notes: "Specific findings"
   reliability:
     status: PASS|CONCERNS|FAIL
-    notes: 'Specific findings'
+    notes: "Specific findings"
   maintainability:
     status: PASS|CONCERNS|FAIL
-    notes: 'Specific findings'
+    notes: "Specific findings"
 
 recommendations:
   immediate: # Must fix before production
-    - action: 'Add rate limiting'
-      refs: ['api/auth/login.ts']
+    - action: "Add rate limiting"
+      refs: ["api/auth/login.ts"]
   future: # Can be addressed later
-    - action: 'Consider caching'
-      refs: ['services/data.ts']
+    - action: "Consider caching"
+      refs: ["services/data.ts"]
 ```
 
 ### Gate Decision Criteria
@@ -11012,10 +11785,10 @@ Generate a comprehensive risk assessment matrix for a story implementation using
 
 ```yaml
 required:
-  - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: 'docs/stories/{epic}.{story}.*.md'
-  - story_title: '{title}' # If missing, derive from story file H1
-  - story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)
+  - story_id: "{epic}.{story}" # e.g., "1.3"
+  - story_path: "docs/stories/{epic}.{story}.*.md"
+  - story_title: "{title}" # If missing, derive from story file H1
+  - story_slug: "{slug}" # If missing, derive from title (lowercase, hyphenated)
 ```
 
 ## Purpose
@@ -11085,14 +11858,14 @@ For each category, identify specific risks:
 
 ```yaml
 risk:
-  id: 'SEC-001' # Use prefixes: SEC, PERF, DATA, BUS, OPS, TECH
+  id: "SEC-001" # Use prefixes: SEC, PERF, DATA, BUS, OPS, TECH
   category: security
-  title: 'Insufficient input validation on user forms'
-  description: 'Form inputs not properly sanitized could lead to XSS attacks'
+  title: "Insufficient input validation on user forms"
+  description: "Form inputs not properly sanitized could lead to XSS attacks"
   affected_components:
-    - 'UserRegistrationForm'
-    - 'ProfileUpdateForm'
-  detection_method: 'Code review revealed missing validation'
+    - "UserRegistrationForm"
+    - "ProfileUpdateForm"
+  detection_method: "Code review revealed missing validation"
 ```
 
 ### 2. Risk Assessment
@@ -11139,20 +11912,20 @@ For each identified risk, provide mitigation:
 
 ```yaml
 mitigation:
-  risk_id: 'SEC-001'
-  strategy: 'preventive' # preventive|detective|corrective
+  risk_id: "SEC-001"
+  strategy: "preventive" # preventive|detective|corrective
   actions:
-    - 'Implement input validation library (e.g., validator.js)'
-    - 'Add CSP headers to prevent XSS execution'
-    - 'Sanitize all user inputs before storage'
-    - 'Escape all outputs in templates'
+    - "Implement input validation library (e.g., validator.js)"
+    - "Add CSP headers to prevent XSS execution"
+    - "Sanitize all user inputs before storage"
+    - "Escape all outputs in templates"
   testing_requirements:
-    - 'Security testing with OWASP ZAP'
-    - 'Manual penetration testing of forms'
-    - 'Unit tests for validation functions'
-  residual_risk: 'Low - Some zero-day vulnerabilities may remain'
-  owner: 'dev'
-  timeline: 'Before deployment'
+    - "Security testing with OWASP ZAP"
+    - "Manual penetration testing of forms"
+    - "Unit tests for validation functions"
+  residual_risk: "Low - Some zero-day vulnerabilities may remain"
+  owner: "dev"
+  timeline: "Before deployment"
 ```
 
 ## Outputs
@@ -11178,12 +11951,12 @@ risk_summary:
   highest:
     id: SEC-001
     score: 9
-    title: 'XSS on profile form'
+    title: "XSS on profile form"
   recommendations:
     must_fix:
-      - 'Add input sanitization & CSP'
+      - "Add input sanitization & CSP"
     monitor:
-      - 'Add security alerts for auth endpoints'
+      - "Add security alerts for auth endpoints"
 ```
 
 ### Output 2: Markdown Report
@@ -11370,10 +12143,10 @@ Create comprehensive test scenarios with appropriate test level recommendations
 
 ```yaml
 required:
-  - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path from core-config.yaml
-  - story_title: '{title}' # If missing, derive from story file H1
-  - story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)
+  - story_id: "{epic}.{story}" # e.g., "1.3"
+  - story_path: "{devStoryLocation}/{epic}.{story}.*.md" # Path from core-config.yaml
+  - story_title: "{title}" # If missing, derive from story file H1
+  - story_slug: "{slug}" # If missing, derive from title (lowercase, hyphenated)
 ```
 
 ## Purpose
@@ -11426,13 +12199,13 @@ For each identified test need, create:
 
 ```yaml
 test_scenario:
-  id: '{epic}.{story}-{LEVEL}-{SEQ}'
-  requirement: 'AC reference'
+  id: "{epic}.{story}-{LEVEL}-{SEQ}"
+  requirement: "AC reference"
   priority: P0|P1|P2|P3
   level: unit|integration|e2e
-  description: 'What is being tested'
-  justification: 'Why this level was chosen'
-  mitigates_risks: ['RISK-001'] # If risk profile exists
+  description: "What is being tested"
+  justification: "Why this level was chosen"
+  mitigates_risks: ["RISK-001"] # If risk profile exists
 ```
 
 ### 5. Validate Coverage
@@ -11574,21 +12347,21 @@ Identify all testable requirements from:
 For each requirement, document which tests validate it. Use Given-When-Then to describe what the test validates (not how it's written):
 
 ```yaml
-requirement: 'AC1: User can login with valid credentials'
+requirement: "AC1: User can login with valid credentials"
 test_mappings:
-  - test_file: 'auth/login.test.ts'
-    test_case: 'should successfully login with valid email and password'
+  - test_file: "auth/login.test.ts"
+    test_case: "should successfully login with valid email and password"
     # Given-When-Then describes WHAT the test validates, not HOW it's coded
-    given: 'A registered user with valid credentials'
-    when: 'They submit the login form'
-    then: 'They are redirected to dashboard and session is created'
+    given: "A registered user with valid credentials"
+    when: "They submit the login form"
+    then: "They are redirected to dashboard and session is created"
     coverage: full
 
-  - test_file: 'e2e/auth-flow.test.ts'
-    test_case: 'complete login flow'
-    given: 'User on login page'
-    when: 'Entering valid credentials and submitting'
-    then: 'Dashboard loads with user data'
+  - test_file: "e2e/auth-flow.test.ts"
+    test_case: "complete login flow"
+    given: "User on login page"
+    when: "Entering valid credentials and submitting"
+    then: "Dashboard loads with user data"
     coverage: integration
 ```
 
@@ -11610,19 +12383,19 @@ Document any gaps found:
 
 ```yaml
 coverage_gaps:
-  - requirement: 'AC3: Password reset email sent within 60 seconds'
-    gap: 'No test for email delivery timing'
+  - requirement: "AC3: Password reset email sent within 60 seconds"
+    gap: "No test for email delivery timing"
     severity: medium
     suggested_test:
       type: integration
-      description: 'Test email service SLA compliance'
+      description: "Test email service SLA compliance"
 
-  - requirement: 'AC5: Support 1000 concurrent users'
-    gap: 'No load testing implemented'
+  - requirement: "AC5: Support 1000 concurrent users"
+    gap: "No load testing implemented"
     severity: high
     suggested_test:
       type: performance
-      description: 'Load test with 1000 concurrent connections'
+      description: "Load test with 1000 concurrent connections"
 ```
 
 ## Outputs
@@ -11638,11 +12411,11 @@ trace:
     full: Y
     partial: Z
     none: W
-  planning_ref: 'qa.qaLocation/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md'
+  planning_ref: "qa.qaLocation/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md"
   uncovered:
-    - ac: 'AC3'
-      reason: 'No test found for password reset timing'
-  notes: 'See qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md'
+    - ac: "AC3"
+      reason: "No test found for password reset timing"
+  notes: "See qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md"
 ```
 
 ### Output 2: Traceability Report
@@ -12081,12 +12854,12 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
 #### 2.1 基础信息填写
 
 ```yaml
-epic_num: '{{epic_number}}'
-story_num: '{{story_number}}'
-story_title_short: '{{story_title}}'
-role: '{{user_role}}'
-action: '{{user_action}}'
-benefit: '{{user_benefit}}'
+epic_num: "{{epic_number}}"
+story_num: "{{story_number}}"
+story_title_short: "{{story_title}}"
+role: "{{user_role}}"
+action: "{{user_action}}"
+benefit: "{{user_benefit}}"
 ```
 
 #### 2.2 数据库设计部分填写
@@ -13916,7 +14689,12 @@ sections:
         rows:
           - ["移动端", "{{mobile_min}}", "{{mobile_max}}", "{{mobile_devices}}"]
           - ["平板", "{{tablet_min}}", "{{tablet_max}}", "{{tablet_devices}}"]
-          - ["桌面端", "{{desktop_min}}", "{{desktop_max}}", "{{desktop_devices}}"]
+          - [
+              "桌面端",
+              "{{desktop_min}}",
+              "{{desktop_max}}",
+              "{{desktop_devices}}",
+            ]
           - ["宽屏", "{{wide_min}}", "-", "{{wide_devices}}"]
       - id: adaptation-patterns
         title: 适配模式