@zeyue0329/xiaoma-cli 1.8.0 → 1.8.1

package/src/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-06-test-story.md

@@ -103,12 +103,13 @@ Create a test results summary:
 
 **IF all ACs pass AND no HIGH severity issues:**
 - Output: "QA testing PASSED. All {ac_count} acceptance criteria verified with real data. Proceeding to completion."
-- **NEXT:** Proceed to step-08 (complete story)
+- **NEXT:** Proceed to step-08 (complete story) [frontmatter: nextStepFile]
 
 **IF any AC fails OR HIGH severity issues found:**
 - Output: "QA testing FAILED. {ac_fail_count} acceptance criteria not met. Issues: {issue_list}"
 - Record test failures in story file under QA Results section
-- **NEXT:** Proceed to step-07 (fix and retest)
+- Set `{fix_source}` = "qa-testing" (this variable will be used in step-07 to route fixes directly to step-08 after correction, since QA issues often don't require code review re-entry)
+- **NEXT:** Proceed to step-07 (fix and retest) [frontmatter: nextStepFile_fail]
 
 ### 7. Pipeline Status Update
 
@@ -142,3 +143,111 @@ Create a test results summary:
 - Skipping acceptance criteria during testing
 - Not verifying database state after write operations
 - Marking tests as PASS without evidence
+
+---
+
+## 测试失败处理流程 (Test Failure Handling)
+
+**当任何acceptance criteria失败时:**
+
+### 1. 失败分类 (Categorize Failures)
+
+对每个失败进行分类:
+
+- **Type A - AC Failure (接受标准失败)**: 核心功能没有达到预期
+  - 示例: 应该返回值X，实际返回值Y
+  - 路由: → step-07 (fix-and-retest)
+  
+- **Type B - Data Integrity Issue (数据完整性问题)**: 数据库状态不正确
+  - 示例: 记录未保存或数据损坏
+  - 路由: → step-07 (fix-and-retest) 并标记为HIGH优先级
+  
+- **Type C - Performance Issue (性能问题)**: 功能正常但超过性能阈值
+  - 示例: API响应时间 > 2秒
+  - 路由: → step-07 (fix-and-retest) 但标记为MEDIUM优先级
+  
+- **Type D - Environment/Test Setup Issue (环境问题)**: 测试环境配置问题
+  - 示例: 数据库连接失败、假数据缺失
+  - 路由: → 修复测试环境，然后重新运行tests
+
+### 2. 重试策略 (Retry Strategy)
+
+**对于Type A和B失败:**
+- 在step-07中作为HIGH优先级修复
+- 每个Type A/B失败最多重试1次在step-06（re-run tests）
+  
+**对于Type C失败（仅性能）:**
+- 如果只有Type C失败，可以有条件地PASS
+- 但必须在story文件中记录性能问题
+- 标记为"KNOWN_PERFORMANCE_ISSUE"
+- 移至backlog作为future optimization
+- 仅在Type A/B都PASS时允许带Type C继续
+
+**对于Type D失败:**
+- 不计入fix iteration（fix-and-retest）
+- 修复测试环境
+- 立即重新运行测试
+
+### 3. 测试覆盖率阈值 (Coverage Thresholds)
+
+**强制要求:**
+- 单元测试覆盖率: >= 75%
+- 集成测试覆盖率: >= 60%
+- 接受标准覆盖率: 100% (所有AC必须有至少1个测试)
+
+**如果未达到:**
+- 不允许进入step-07
+- 回到开发阶段添加缺失的tests
+- Type: AC-Incomplete failure → 标记story为"NEEDS_MORE_TESTS"
+
+### 4. 记录失败详情 (Document Failures)
+
+在Story文件的"QA Results"部分记录:
+
+```markdown
+## QA Results
+
+**Overall Status:** FAILED - 2/5 ACs passed
+
+### Failed Tests
+- **AC#2 (Type A):** [Description] 
+  - Expected: [X]
+  - Actual: [Y]
+  - Root Cause: [Analysis]
+  - Fix Priority: HIGH
+  
+- **AC#4 (Type C):** [Performance]
+  - Threshold: 1s
+  - Actual: 2.3s
+  - Fix Priority: MEDIUM (Known issue, defer if needed)
+
+### Coverage Summary
+- Unit: 72% (Below 75% threshold)
+- Integration: 65%
+- AC Coverage: 100%
+
+### Recommended Next Step
+- Re-run step-07 to fix AC#2 (HIGH)
+- Consider Type C as known limitation unless time allows
+```
+
+### 5. 条件通过规则 (Conditional Pass)
+
+故事可以在以下条件下**有条件通过**到step-07:
+
+✅ **全部Type A/B失败已解决**
+✅ **至少80%的接受标准通过** 
+✅ **无Critical数据完整性问题**
+❌ **Type C (性能)失败不阻止进度** (但需要记录)
+❌ **测试覆盖率 < 60% 则必须返回修复**
+
+### 6. 向step-07传递信息 (Hand-off to step-07)
+
+设置以下变量供step-07使用:
+
+```
+{fix_source} = "qa-testing"
+{failure_categories} = [Type A count, Type B count, Type C count]
+{high_priority_issues} = [list]
+{performance_known_issues} = [list]  // For conditional pass scenarios
+```

package/src/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-07-fix-and-retest.md

@@ -126,3 +126,112 @@ After all fixes are applied:
 - Introducing new regressions while fixing existing issues
 - Exceeding `{max_fix_iterations}` fix iterations without resolution
 - Not running regression tests after each fix
+
+---
+
+## 当超过最大修复迭代次数 (Escalation Path: Beyond Max Fix Iterations)
+
+**触发条件:** `{fix_iteration}` > `{max_fix_iterations}` (默认 > 5)
+
+**Escalation Protocol:**
+
+### 1. 生成Escalation Report
+
+文档所有修复尝试和失败原因:
+
+```
+ESCALATION REPORT: Story {current_story_key}
+==========================================
+Status: FIX LIMIT EXCEEDED
+Fix Iterations Attempted: {max_fix_iterations}
+Unresolved Issues:
+  - [Issue 1]: [Root Cause Analysis]
+  - [Issue 2]: [Root Cause Analysis]
+  
+Pattern Analysis:
+  - Recurring issue? [Yes/No] — [Description]
+  - Root cause identified? [Yes/No]
+  - Architectural blocker? [Yes/No]
+  
+Timeline Impact: [number] days
+Recommended Action: [A/B/C below]
+```
+
+### 2. 通知团队 (Owner Notification)
+
+发送通知至:
+- **Primary:** Story Owner / Scrum Master (Mary)
+- **Secondary:** Tech Lead / Architect (Winston)
+
+**Notification Template:**
+
+```
+URGENT: Story {current_story_key} - Fix Limit Reached
+
+Summary: After {max_fix_iterations} fix iterations, the following issues remain unresolved:
+- [Issue list]
+
+Root Cause Analysis:
+- [Analysis summary]
+
+Recommended Actions:
+A) Mark as "Blocked" - Investigate architectural changes needed
+B) Reduce scope - Defer failing AC to next iteration  
+C) Re-assign to Tech Lead for deep investigation
+D) Revert changes and restart implementation from scratch
+
+Timeline: Requires decision within [4 hours / 1 day]
+Severity: BLOCKING SPRINT PROGRESS
+```
+
+### 3. 处理选项 (Handling Options)
+
+**选项 A - 标记为Blocked:**
+- 更新story状态为 `BLOCKED_INVESTIGATION`
+- 记录blocking factors
+- Escalate to Architect (Winston) for architectural review
+- 移出当前sprint backlog
+
+**选项 B - 缩小范围 (Reduce Scope):**
+- 识别哪些acceptance criteria无法在{max_fix_iterations}内完成
+- 将这些AC移至"acceptance-criteria-deferred"部分
+- 标记为"READY_FOR_TESTING"（简化的AC集合）
+- 继续进入step-08
+
+**选项 C - 重新分配 (Tech Lead Deep Dive):**
+- 暂停当前story处理
+- 分配给Tech Lead (Winston) 进行深度root cause分析
+- 预计时间: 2-4小时的深度分析
+- 结果: 要么找到fix，要么confirm需要选项A或B
+
+**选项 D - 重新开始 (Fresh Start):**
+- 回退所有代码更改到step-04开始前的状态
+- 重新执行step-04到step-07
+- 仅在其他选项都不可行时使用
+- 添加至"lessons learned"文档
+
+### 4. Story状态管理
+
+**设置Story Meta字段:**
+```
+escalation_status: ESCALATED
+escalation_date: {current_timestamp}
+escalation_owner: {person_assigned}
+recommended_action: [A/B/C/D]
+estimated_resolution_time: [hours]
+```
+
+### 5. 防止进度堵塞 (Prevent Sprint Blocking)
+
+- 不允许story卡在此步骤超过{max_fix_iterations} + 4小时
+- 自动移至Scrum Master队列以处理escalation
+- 在sprint status中标记为"NEEDS_DECISION"
+- 不将此issue计入sprint velocity（因为未完成）
+
+### 6. 恢复进度 (Recovery Process)
+
+一旦Escalation决策完成:
+- 如果选择 A: Story移至 `BLOCKED` 状态，等待Architect反馈
+- 如果选择 B: 回到step-08 (complete story)，使用简化的AC集合
+- 如果选择 C: Architect执行分析，结果完成后回到step-07
+- 如果选择 D: Story重置到step-04，重新开始整个cycle

package/src/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-08-complete-story.md

@@ -17,8 +17,8 @@ nextStepFile: "./step-09-cycle-check.md"
 ### 1. Final Validation
 
 Before marking complete, verify all gates:
-1. Read the COMPLETE story file at `{current_story_path}`
-2. Verify ALL tasks and subtasks are marked [x]
+1. **Fresh Read:** Read the COMPLETE story file at `{current_story_path}` directly from disk (not from cache or prior state). This is critical because step-07 may have modified the file (e.g., updated task checkboxes, changed story status), and you MUST verify the current on-disk state, not a stale in-memory version.
+2. Verify ALL tasks and subtasks are marked [x], [X], or [✓] (case-insensitive, all formats accepted)
 3. Verify ALL acceptance criteria have been tested and passed
 4. Verify no unresolved HIGH or MEDIUM issues remain
 5. Verify the full test suite passes

package/src/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-09-cycle-check.md

@@ -32,10 +32,12 @@ nextStepFile: null
    - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
    - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
    - Status value equals "backlog"
+   - If found: Set `{found_status}` = "backlog"
 5. If no "backlog" story is found, search again for the FIRST story where:
    - Key matches the same pattern (not epic, not retrospective)
    - Status value equals "ready-for-dev"
    - *(Mirrors step-01's initial story selection: "backlog, or ready-for-dev if no backlog")*
+   - If found: Set `{found_status}` = "ready-for-dev"
 
 ### 3. Evaluate Next Story
 
@@ -43,6 +45,7 @@ nextStepFile: null
 - Set `{current_story_key}` = found story key
 - Set `{current_story_path}` = "" (will be set during creation/validation)
 - Set `{fix_iteration}` = 0
+- *(Note: `{found_status}` was already set in section 2 above — "backlog" or "ready-for-dev" — and is used in the progress checkpoint output below.)*
 
 **3.5. Batch Mode Progress Checkpoint**
 

package/src/xmc/workflows/4-implementation/auto-story-pipeline/workflow.md

@@ -34,9 +34,10 @@ This uses **step-file architecture** for focused execution across a long-running
 
 - `{pipeline_mode}` — "single" (one story) or "batch" (all backlog stories)
 - `{current_story_key}` — Key of story being processed (e.g., "1-2-user-auth")
-- `{current_story_path}` — Full path to current story file (derived in step-01 after resolving `{current_story_key}`; re-set in step-02 skip branch for batch cycles)
+- `{current_story_path}` — Full path to current story file (derived in step-01 after resolving `{current_story_key}`; re-set in step-02 skip branch for batch cycles). **CRITICAL:** In batch mode, this variable is reset for each story iteration (step-09 → step-02 loop). Whenever re-reading the story file in subsequent steps (e.g., step-08 final validation, step-03 re-checks), always perform a FRESH read directly from disk using this path variable. Do NOT rely on cached/stale in-memory state from earlier steps in the same cycle, as intermediate steps (step-04, step-05, step-06, step-07) may have modified the file
 - `{fix_iteration}` — Bug fix loop counter (max controlled by `{max_fix_iterations}`, default 5; reset per story)
 - `{max_fix_iterations}` — Maximum fix-and-retest cycles per story (configurable via `max_fix_iterations` in config.yaml; default 5 if not set)
+- `{fix_source}` — Origin of failures being fixed in step-07: "code-review" (step-05 routed here with unresolvable issues), "qa-testing" (step-06 routed here with test failures), or "mixed" (both code review and QA issues); set in step-07 section 2; determines post-fix routing (code-review/mixed → inline targeted re-check before step-08; qa-testing → step-08 directly)
 - `{stories_completed}` — Count of stories completed in this pipeline run
 - `{pipeline_status}` — Current pipeline phase for tracking
 - `{validation_attempt}` — Story validation attempt counter (used in step-03, max 3; re-initialized at start of step-03 for each story)
@@ -46,6 +47,7 @@ This uses **step-file architecture** for focused execution across a long-running
 - `{in_progress_count}` — Count of stories with status "in-progress" (initialized in step-01; refreshed in step-09)
 - `{review_count}` — Count of stories with status "review" (initialized in step-01; refreshed in step-09)
 - `{done_count}` — Count of stories with status "done" (initialized in step-01; refreshed in step-09)
+- `{found_status}` — Status of the next processable story found during step-09 section 2 search: "backlog" or "ready-for-dev"; explicitly set alongside `{current_story_key}` when a story is selected; used in section 3.5 progress checkpoint output; local to step-09 and not persisted between stories
 
 ### Status Machine
 

package/tools/cli/installers/lib/ide/templates/combined/gemini-task.toml

@@ -1,6 +1,6 @@
-description = "Executes the {{name}} task from the BMAD Method."
+description = "Executes the {{name}} task from the XiaoMa Method."
 prompt = """
-Execute the BMAD '{{name}}' task.
+Execute the XiaoMa '{{name}}' task.
 
 TASK INSTRUCTIONS:
 1. LOAD the task file from {project-root}/{{bmadFolderName}}/{{path}}

package/tools/cli/installers/lib/ide/templates/combined/gemini-tool.toml

@@ -1,6 +1,6 @@
-description = "Executes the {{name}} tool from the BMAD Method."
+description = "Executes the {{name}} tool from the XiaoMa Method."
 prompt = """
-Execute the BMAD '{{name}}' tool.
+Execute the XiaoMa '{{name}}' tool.
 
 TOOL INSTRUCTIONS:
 1. LOAD the tool file from {project-root}/{{bmadFolderName}}/{{path}}

package/tools/cli/installers/lib/ide/templates/combined/gemini-workflow-yaml.toml

@@ -1,6 +1,6 @@
 description = '{{description}}'
 prompt = """
-Execute the BMAD '{{name}}' workflow.
+Execute the XiaoMa '{{name}}' workflow.
 
 CRITICAL: This is a structured YAML workflow. Follow these steps precisely:
 

package/tools/cli/installers/lib/ide/templates/combined/gemini-workflow.toml

@@ -1,6 +1,6 @@
 description = '{{description}}'
 prompt = """
-Execute the BMAD '{{name}}' workflow.
+Execute the XiaoMa '{{name}}' workflow.
 
 CRITICAL: You must load and follow the workflow definition exactly.
 

package/tools/cli/lib/cli-utils.js

@@ -25,17 +25,17 @@ const CLIUtils = {
 
     // ASCII art logo
     const logo = [
-      '    ██████╗ ███╗   ███╗ █████╗ ██████╗ ™',
-      '    ██╔══██╗████╗ ████║██╔══██╗██╔══██╗',
-      '    ██████╔╝██╔████╔██║███████║██║  ██║',
-      '    ██╔══██╗██║╚██╔╝██║██╔══██║██║  ██║',
-      '    ██████╔╝██║ ╚═╝ ██║██║  ██║██████╔╝',
-      '    ╚═════╝ ╚═╝     ╚═╝╚═╝  ╚═╝╚═════╝',
+      '  ██╗  ██╗██╗ █████╗  ██████╗ ███╗   ███╗ █████╗',
+      '  ╚██╗██╔╝██║██╔══██╗██╔═══██╗████╗ ████║██╔══██╗',
+      '   ╚███╔╝ ██║███████║██║   ██║██╔████╔██║███████║',
+      '   ██╔██╗ ██║██╔══██║██║   ██║██║╚██╔╝██║██╔══██║',
+      '  ██╔╝ ██╗██║██║  ██║╚██████╔╝██║ ╚═╝ ██║██║  ██║',
+      '  ╚═╝  ╚═╝╚═╝╚═╝  ╚═╝ ╚═════╝ ╚═╝     ╚═╝╚═╝  ╚═╝',
     ]
       .map((line) => color.yellow(line))
       .join('\n');
 
-    const tagline = '    Build More, Architect Dreams';
+    const tagline = '      AI-Driven Agile Development';
 
     await prompts.box(`${logo}\n${tagline}`, `v${version}`, {
       contentAlign: 'center',