@zeyue0329/xiaoma-cli 1.0.49 → 6.0.0-alpha.14

package/src/modules/xmc/workflows/auto-iteration/resume.md

@@ -0,0 +1,254 @@
+# 恢复执行工作流
+
+> **工作流 ID**: resume
+> **触发命令**: `*resume`
+> **智能体**: Phoenix (全自动化迭代开发编排器)
+
+---
+
+## 功能说明
+
+从上次中断的位置恢复执行全自动迭代开发流程。支持：
+- 阶段级恢复：从某个阶段重新开始
+- 任务级恢复：从某个任务继续执行
+- 故事级恢复：从某个故事继续开发
+
+---
+
+## 执行指令
+
+当用户输入 `*resume` 时：
+
+```yaml
+task: resume_execution
+actions:
+  - name: 读取状态文件
+    file: "auto-iteration-status.yaml"
+
+  - name: 确定恢复点
+    analyze:
+      - 最后完成的阶段
+      - 当前进行中的任务
+      - 上次执行的位置
+
+  - name: 验证恢复条件
+    check:
+      - 必要文件是否存在
+      - 依赖是否满足
+      - 知识库是否可用
+
+  - name: 恢复执行
+    continue_from: last_checkpoint
+```
+
+---
+
+## 恢复场景
+
+### 场景 1: 阶段中断
+
+```yaml
+scenario: phase_interrupted
+example:
+  last_state:
+    phase: "phase_3_design"
+    status: "in_progress"
+    task: "API 设计"
+
+  resume_action:
+    - 加载 Phase 3 上下文
+    - 从 "API 设计" 任务继续
+    - 完成后继续后续任务
+
+  output: |
+    ## 恢复执行
+
+    检测到上次执行在 Phase 3 (架构设计) 中断。
+
+    **中断位置**: API 设计
+    **已完成任务**: 现有架构分析、技术方案设计、数据模型设计
+    **待完成任务**: API 设计、技术决策记录、文件变更清单
+
+    正在从 "API 设计" 任务继续执行...
+```
+
+### 场景 2: 故事开发中断
+
+```yaml
+scenario: story_development_interrupted
+example:
+  last_state:
+    phase: "phase_4_develop"
+    current_story: "STORY-003"
+    story_status: "in_progress"
+    current_task: "TASK-002"
+    tdd_phase: "green"
+
+  resume_action:
+    - 加载 STORY-003 上下文
+    - 从 TASK-002 的 Green Phase 继续
+    - 运行测试验证当前状态
+    - 继续实现
+
+  output: |
+    ## 恢复执行
+
+    检测到上次执行在 Phase 4 (开发实现) 中断。
+
+    **当前故事**: STORY-003 - 偏好导入
+    **当前任务**: TASK-002 - 实现 importService
+    **TDD 阶段**: Green (实现代码)
+
+    正在验证当前状态...
+    - 测试文件存在: ✅
+    - 部分实现存在: ✅
+    - 测试状态: 2/5 通过
+
+    正在从 TASK-002 继续实现...
+```
+
+### 场景 3: 测试失败后恢复
+
+```yaml
+scenario: test_failure_recovery
+example:
+  last_state:
+    phase: "phase_5_test"
+    status: "blocked"
+    blocking_reason: "3 tests failed"
+    failed_tests:
+      - "preferenceService.test.ts:45"
+      - "preferenceService.test.ts:67"
+      - "importController.test.ts:23"
+
+  resume_action:
+    - 分析失败测试
+    - 查询知识库获取解决方案
+    - 返回 Phase 4 修复代码
+    - 重新运行测试
+
+  output: |
+    ## 恢复执行
+
+    检测到上次执行在 Phase 5 (测试验证) 因测试失败而阻塞。
+
+    **失败测试**:
+    1. preferenceService.test.ts:45 - 断言失败
+    2. preferenceService.test.ts:67 - 超时
+    3. importController.test.ts:23 - 未捕获异常
+
+    **恢复策略**:
+    1. 分析失败原因
+    2. 返回 Phase 4 修复相关代码
+    3. 重新运行测试验证
+
+    正在分析失败原因...
+```
+
+---
+
+## 恢复前检查
+
+```yaml
+pre_resume_checks:
+  - name: 状态文件检查
+    check: "auto-iteration-status.yaml 存在且有效"
+    if_fail: "无法恢复，请重新开始执行"
+
+  - name: 产出物检查
+    check: "已生成的产出物完整"
+    if_fail: "部分产出物丢失，需要重新生成"
+
+  - name: 知识库检查
+    check: "知识库可访问"
+    if_fail: "知识库不可用，部分功能受限"
+
+  - name: 代码库检查
+    check: "代码库状态一致"
+    if_fail: "检测到代码变更，需要人工确认"
+```
+
+---
+
+## 恢复选项
+
+```markdown
+## 恢复选项
+
+检测到可以从以下位置恢复：
+
+### 选项 1: 从当前位置继续（推荐）
+- **位置**: Phase 4 - STORY-003 - TASK-002
+- **描述**: 从上次中断的确切位置继续
+- **命令**: `*resume`
+
+### 选项 2: 从阶段开始重新执行
+- **位置**: Phase 4 开始
+- **描述**: 重新执行整个 Phase 4
+- **命令**: `*resume --phase=4`
+
+### 选项 3: 从故事开始重新执行
+- **位置**: STORY-003 开始
+- **描述**: 重新执行当前故事
+- **命令**: `*resume --story=STORY-003`
+
+### 选项 4: 跳过当前任务
+- **位置**: STORY-003 - TASK-003
+- **描述**: 跳过当前任务，继续下一个
+- **命令**: `*resume --skip-task`
+- **警告**: 可能导致功能不完整
+
+请选择恢复选项，或直接输入 `*resume` 从当前位置继续。
+```
+
+---
+
+## 恢复执行流程
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                      恢复执行流程                            │
+├─────────────────────────────────────────────────────────────┤
+│  1. 读取状态文件                                             │
+│     └─ 确定上次执行位置                                      │
+├─────────────────────────────────────────────────────────────┤
+│  2. 预恢复检查                                               │
+│     ├─ 验证产出物完整性                                      │
+│     ├─ 验证代码库状态                                        │
+│     └─ 验证知识库可用性                                      │
+├─────────────────────────────────────────────────────────────┤
+│  3. 加载上下文                                               │
+│     ├─ 加载阶段上下文                                        │
+│     ├─ 加载任务上下文                                        │
+│     └─ 加载知识库索引                                        │
+├─────────────────────────────────────────────────────────────┤
+│  4. 恢复执行                                                 │
+│     └─ 从断点继续执行                                        │
+├─────────────────────────────────────────────────────────────┤
+│  5. 更新状态                                                 │
+│     └─ 记录恢复执行信息                                      │
+└─────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## 状态更新
+
+恢复执行时更新状态文件：
+
+```yaml
+execution:
+  status: "in_progress"
+  resumed_at: "[时间戳]"
+  resume_count: 1
+  resume_from:
+    phase: "phase_4_develop"
+    story: "STORY-003"
+    task: "TASK-002"
+
+resume_history:
+  - timestamp: "[时间戳]"
+    from_phase: "phase_4_develop"
+    from_task: "TASK-002"
+    reason: "manual_resume"
+```

package/src/modules/xmc/workflows/auto-iteration/status.md

@@ -0,0 +1,194 @@
+# 执行状态查看
+
+> **工作流 ID**: status
+> **触发命令**: `*status`
+> **智能体**: Phoenix (全自动化迭代开发编排器)
+
+---
+
+## 功能说明
+
+查看当前自动迭代开发的执行状态，包括：
+- 当前所处阶段
+- 已完成的工作
+- 正在进行的任务
+- 阻塞问题
+- 预估剩余工作
+
+---
+
+## 执行指令
+
+当用户输入 `*status` 时，读取并展示执行状态：
+
+```yaml
+task: show_status
+actions:
+  - name: 读取状态文件
+    file: "auto-iteration-status.yaml"
+
+  - name: 读取 Sprint 状态
+    file: "sprint-status.yaml"
+    if: exists
+
+  - name: 汇总并展示
+    format: markdown
+```
+
+---
+
+## 状态展示格式
+
+```markdown
+# 🔄 全自动迭代开发 - 执行状态
+
+## 基本信息
+- **执行 ID**: iter-2024-001
+- **开始时间**: 2024-01-15 10:00:00
+- **当前状态**: 🟢 执行中
+- **耗时**: 2h 30m
+
+---
+
+## 阶段进度
+
+```
+Phase 1: 需求分析    ████████████████████ 100% ✅
+Phase 2: 需求规划    ████████████████████ 100% ✅
+Phase 3: 架构设计    ████████████████████ 100% ✅
+Phase 4: 开发实现    ████████████░░░░░░░░  60% 🔄
+Phase 5: 测试验证    ░░░░░░░░░░░░░░░░░░░░   0% ⏳
+```
+
+**当前阶段**: Phase 4 - 开发实现
+**当前任务**: 实现 STORY-003
+
+---
+
+## Sprint 进度
+
+| 故事 ID | 标题 | 点数 | 状态 |
+|--------|------|-----|------|
+| STORY-001 | 用户偏好设置 | 3 | ✅ Done |
+| STORY-002 | 偏好导出 | 5 | ✅ Done |
+| STORY-003 | 偏好导入 | 5 | 🔄 In Progress |
+| STORY-004 | 偏好同步 | 5 | ⏳ Todo |
+| STORY-005 | 偏好备份 | 3 | ⏳ Todo |
+
+**进度**: 8/21 点 (38%)
+**完成故事**: 2/5
+
+---
+
+## 阻塞问题
+
+当前无阻塞问题。
+
+---
+
+## 知识库使用统计
+
+| 类型 | 查询次数 | 命中次数 | 命中率 |
+|-----|---------|---------|-------|
+| 业务规则 | 15 | 12 | 80% |
+| 技术规范 | 23 | 21 | 91% |
+| 架构模式 | 8 | 7 | 88% |
+
+---
+
+## 产出物清单
+
+### 已生成
+- ✅ requirement-analysis.md
+- ✅ prd.md
+- ✅ epics/ (3 个史诗)
+- ✅ stories/ (5 个故事)
+- ✅ architecture.md
+- ✅ adr/ (3 个决策记录)
+- 🔄 src/ (8/12 文件)
+- 🔄 tests/ (30/45 测试)
+
+### 待生成
+- ⏳ test-report.md
+- ⏳ quality-report.md
+
+---
+
+## 预估
+
+- **预估剩余时间**: 1h 30m
+- **预估完成时间**: 2024-01-15 14:00:00
+
+---
+
+## 操作建议
+
+当前执行正常，无需干预。
+
+如需操作：
+- `*resume` - 从当前位置继续执行
+- `*kb-query [问题]` - 查询知识库
+- `*phase-develop` - 单独执行开发阶段
+```
+
+---
+
+## 状态文件格式
+
+```yaml
+# auto-iteration-status.yaml
+execution:
+  id: "iter-2024-001"
+  started_at: "2024-01-15T10:00:00Z"
+  status: "in_progress"  # pending | in_progress | completed | blocked | failed
+
+current:
+  phase: "phase_4_develop"
+  phase_name: "开发实现"
+  task: "实现 STORY-003"
+  story_id: "STORY-003"
+
+phases:
+  phase_1_analyze:
+    status: "completed"
+    started_at: "2024-01-15T10:00:00Z"
+    completed_at: "2024-01-15T10:15:00Z"
+    duration: "15m"
+
+  phase_2_plan:
+    status: "completed"
+    started_at: "2024-01-15T10:15:00Z"
+    completed_at: "2024-01-15T10:45:00Z"
+    duration: "30m"
+
+  phase_3_design:
+    status: "completed"
+    started_at: "2024-01-15T10:45:00Z"
+    completed_at: "2024-01-15T11:30:00Z"
+    duration: "45m"
+
+  phase_4_develop:
+    status: "in_progress"
+    started_at: "2024-01-15T11:30:00Z"
+    progress: 60%
+    current_story: "STORY-003"
+
+  phase_5_test:
+    status: "pending"
+
+blocking_issues: []
+
+knowledge_base:
+  queries_total: 46
+  queries_hit: 40
+  hit_rate: 87%
+
+outputs:
+  generated:
+    - "requirement-analysis.md"
+    - "prd.md"
+    - "architecture.md"
+  pending:
+    - "test-report.md"
+    - "quality-report.md"
+```

package/src/modules/xmc/workflows/auto-iteration/templates/auto-iteration-status.template.yaml

@@ -0,0 +1,142 @@
+# 全自动迭代开发状态追踪模板
+# Auto-Iteration Status Template
+
+execution:
+  id: "{iteration_id}"
+  name: "{iteration_name}"
+  started_at: "{start_timestamp}"
+  status: "pending"  # pending | in_progress | completed | blocked | failed
+
+  inputs:
+    requirement_document: "{requirement_doc_path}"
+    knowledge_base:
+      business: "{business_kb_path}"
+      technical: "{technical_kb_path}"
+    project_path: "{project_root}"
+
+current:
+  phase: null
+  phase_name: null
+  task: null
+  story_id: null
+
+phases:
+  phase_1_analyze:
+    status: "pending"
+    started_at: null
+    completed_at: null
+    duration: null
+    outputs: []
+    metrics:
+      features_identified: 0
+      kb_match_rate: 0
+      implicit_requirements: 0
+      conflicts_found: 0
+      risks_identified: 0
+
+  phase_2_plan:
+    status: "pending"
+    started_at: null
+    completed_at: null
+    duration: null
+    outputs: []
+    metrics:
+      total_frs: 0
+      total_nfrs: 0
+      total_epics: 0
+      total_stories: 0
+      total_story_points: 0
+
+  phase_3_design:
+    status: "pending"
+    started_at: null
+    completed_at: null
+    duration: null
+    outputs: []
+    metrics:
+      new_files: 0
+      modified_files: 0
+      adrs_created: 0
+      api_endpoints: 0
+
+  phase_4_develop:
+    status: "pending"
+    started_at: null
+    completed_at: null
+    duration: null
+    outputs: []
+    metrics:
+      stories_completed: 0
+      total_points_completed: 0
+      files_created: 0
+      files_modified: 0
+      tests_written: 0
+      test_coverage: 0
+      code_review_pass_rate: 0
+
+  phase_5_test:
+    status: "pending"
+    started_at: null
+    completed_at: null
+    duration: null
+    outputs: []
+    metrics:
+      total_tests: 0
+      passed_tests: 0
+      failed_tests: 0
+      pass_rate: 0
+      code_coverage: 0
+      quality_gates_passed: false
+      nfr_validated: false
+
+blocking_issues: []
+# 示例:
+# - id: "BLOCK-001"
+#   phase: "phase_4_develop"
+#   story: "STORY-003"
+#   description: "测试持续失败"
+#   created_at: "{timestamp}"
+#   resolution_attempts: 0
+#   status: "open"  # open | resolved | escalated
+
+knowledge_base:
+  queries_total: 0
+  queries_hit: 0
+  hit_rate: 0
+  queries_log: []
+  # 示例:
+  # - query: "用户认证规则"
+  #   result: "found"
+  #   source: "business-rules/auth.md"
+  #   timestamp: "{timestamp}"
+
+outputs:
+  generated: []
+  pending:
+    - "requirement-analysis.md"
+    - "prd.md"
+    - "architecture.md"
+    - "test-report.md"
+    - "quality-report.md"
+
+resume_history: []
+# 示例:
+# - timestamp: "{timestamp}"
+#   from_phase: "phase_4_develop"
+#   from_task: "TASK-002"
+#   reason: "manual_resume"
+
+decision_log: []
+# 示例:
+# - id: "DEC-001"
+#   phase: "phase_3_design"
+#   decision: "使用 Repository Pattern"
+#   basis: "tech-kb/architecture-patterns.md"
+#   timestamp: "{timestamp}"
+
+warnings: []
+# 示例:
+# - phase: "phase_1_analyze"
+#   type: "low_kb_match"
+#   message: "业务规则匹配率低于阈值"
+#   timestamp: "{timestamp}"

package/src/modules/xmc/workflows/bmad-quick-flow/create-tech-spec/instructions.md

@@ -0,0 +1,115 @@
+# Create Tech-Spec - Spec Engineering for AI Development
+
+<workflow>
+
+<critical>Communicate in {communication_language}, tailored to {user_skill_level}</critical>
+<critical>Generate documents in {document_output_language}</critical>
+<critical>Conversational spec engineering - ask questions, investigate code, produce complete spec</critical>
+<critical>Spec must contain ALL context a fresh dev agent needs to implement it</critical>
+
+<checkpoint-handlers>
+  <on-select key="a">Load and execute {advanced_elicitation}, then return to current step</on-select>
+  <on-select key="p">Load and execute {party_mode_workflow}, then return to current step</on-select>
+  <on-select key="b">Load and execute {quick_dev_workflow} with the tech-spec file</on-select>
+</checkpoint-handlers>
+
+<step n="1" goal="Understand what the user wants to build">
+
+<action>Greet {user_name} and ask them to describe what they want to build or change.</action>
+
+<action>Ask clarifying questions: problem, who's affected, scope, constraints, existing code?</action>
+
+<action>Check for existing context in {output_folder} and {sprint_artifacts}</action>
+
+<checkpoint title="Problem Understanding">
+[a] Advanced Elicitation  [c] Continue  [p] Party Mode
+</checkpoint>
+
+</step>
+
+<step n="2" goal="Investigate existing code (if applicable)">
+
+<action>If brownfield: get file paths, read code, identify patterns/conventions/dependencies</action>
+
+<action>Document: tech stack, code patterns, files to modify, test patterns</action>
+
+<checkpoint title="Context Gathered">
+[a] Advanced Elicitation  [c] Continue  [p] Party Mode
+</checkpoint>
+
+</step>
+
+<step n="3" goal="Generate the technical specification">
+
+<action>Create tech-spec using this structure:
+
+```markdown
+# Tech-Spec: {title}
+
+**Created:** {date}
+**Status:** Ready for Development
+
+## Overview
+
+### Problem Statement
+
+### Solution
+
+### Scope (In/Out)
+
+## Context for Development
+
+### Codebase Patterns
+
+### Files to Reference
+
+### Technical Decisions
+
+## Implementation Plan
+
+### Tasks
+
+- [ ] Task 1: Description
+- [ ] Task 2: Description
+
+### Acceptance Criteria
+
+- [ ] AC 1: Given/When/Then
+- [ ] AC 2: ...
+
+## Additional Context
+
+### Dependencies
+
+### Testing Strategy
+
+### Notes
+```
+
+</action>
+
+<action>Save to {sprint_artifacts}/tech-spec-{slug}.md</action>
+
+</step>
+
+<step n="4" goal="Review and finalize">
+
+<action>Present spec to {user_name}, ask if it captures intent, make changes as needed</action>
+
+<output>**Tech-Spec Complete!**
+
+Saved to: {sprint_artifacts}/tech-spec-{slug}.md
+
+[a] Advanced Elicitation - refine further
+[b] Begin Development (not recommended - fresh context better)
+[d] Done - exit
+[p] Party Mode - get feedback
+
+**Recommended:** Run `dev-spec {sprint_artifacts}/tech-spec-{slug}.md` in fresh context.
+</output>
+
+<ask>Choice (a/b/d/p):</ask>
+
+</step>
+
+</workflow>