@zeyue0329/xiaoma-cli 1.0.49 → 1.6.4

package/xiaoma-core/tasks/serial-development-orchestration.md

@@ -1,426 +0,0 @@
-# Serial Development Orchestration - 串行开发编排
-
-## Task Overview
-
-**任务名称**: 串行开发编排  
-**任务ID**: serial-development-orchestration  
-**分类**: 开发流程编排  
-**复杂度**: ⭐⭐⭐⭐⭐
-
-## Task Description
-
-基于用户故事依赖关系图，智能编排严格串行开发流水线，确保每个任务100%完成后再启动下一个任务，特别是当后续工作依赖前面工作结果时，必须保障前一项工作已经完成并且质量百分百过关。
-
-## Input Requirements
-
-### 必需输入
-
-1. **项目故事积压清单** (project_story_backlog.md)
-   - 完整的用户故事清单
-   - 优先级排序和严格执行顺序
-
-2. **故事依赖关系图** (story_dependency_graph.yaml)
-   - 故事间严格依赖关系
-   - 串行执行路径识别
-
-3. **开发资源配置** (development_resources.yaml)
-   - 单线程开发团队配置
-   - 串行处理模式
-
-## Processing Steps
-
-### 第1步: 严格依赖关系分析
-
-```yaml
-dependency_analysis:
-  graph_processing:
-    - topological_sorting: 拓扑排序确定严格执行顺序
-    - critical_path_identification: 关键路径串行识别
-    - sequential_order_validation: 串行顺序验证
-    - dependency_completeness_check: 依赖完整性检查
-
-  execution_sequence:
-    sequential_stages:
-      - stage_1_foundation: 基础依赖故事(第一优先级)
-      - stage_2_core: 核心业务故事(基础完成后)
-      - stage_3_features: 特性功能故事(核心完成后)
-      - stage_4_optimization: 优化增强故事(特性完成后)
-```
-
-### 第2步: 串行流水线设计
-
-```yaml
-pipeline_design:
-  pipeline_architecture:
-    execution_mode: strict_sequential
-    pipeline_count: 1 # 单一串行流水线
-
-    serial_pipeline:
-      focus: "严格串行执行所有故事"
-      execution_policy: "one_task_at_a_time"
-      completion_requirement: "100%_before_next"
-
-      story_execution_order:
-        priority_1_foundation: ["用户认证", "权限管理", "基础数据模型"]
-        priority_2_core: ["主要业务流程", "核心数据操作"]
-        priority_3_features: ["扩展功能", "用户体验优化"]
-        priority_4_support: ["监控", "配置", "工具功能"]
-
-  quality_gates:
-    strict_validation:
-      - completion_verification: 100%完成度验证
-      - quality_assurance: 质量标准达标
-      - integration_testing: 集成测试通过
-      - dependency_satisfaction: 依赖满足验证
-```
-
-### 第3步: 串行同步点设计
-
-```yaml
-synchronization_design:
-  sync_points:
-    foundation_completion:
-      trigger: "基础故事100%完成"
-      validation: "基础API和数据模型完全就绪"
-      quality_gate: "通过所有测试和质量检查"
-      next_stage: "核心业务开发启动"
-
-    core_business_completion:
-      trigger: "核心业务故事100%完成"
-      validation: "主要业务流程完全就绪"
-      quality_gate: "通过所有集成测试"
-      next_stage: "特性功能开发启动"
-
-    features_completion:
-      trigger: "特性功能故事100%完成"
-      validation: "所有特性功能完全就绪"
-      quality_gate: "通过端到端测试"
-      next_stage: "优化支撑功能启动"
-
-    final_completion:
-      trigger: "所有故事100%完成"
-      validation: "完整产品就绪"
-      quality_gate: "通过最终验收测试"
-      next_stage: "项目交付准备"
-```
-
-### 第4步: 质量门控实施
-
-```yaml
-quality_gates:
-  gate_enforcement:
-    strict_mode: enabled
-    bypass_allowed: false
-
-    gate_1_foundation:
-      requirements:
-        - code_coverage: ">=95%"
-        - unit_tests: "all_passing"
-        - integration_tests: "all_passing"
-        - code_quality: "A_grade"
-
-    gate_2_core:
-      requirements:
-        - api_tests: "all_passing"
-        - business_logic_tests: "all_passing"
-        - database_tests: "all_passing"
-        - performance_tests: "baseline_met"
-
-    gate_3_features:
-      requirements:
-        - feature_tests: "all_passing"
-        - ui_tests: "all_passing"
-        - cross_browser_tests: "all_passing"
-        - accessibility_tests: "all_passing"
-
-    gate_4_final:
-      requirements:
-        - end_to_end_tests: "all_passing"
-        - security_scan: "no_critical_issues"
-        - performance_benchmark: "meets_requirements"
-        - user_acceptance: "approved"
-```
-
-### 第5步: 执行监控和控制
-
-```yaml
-execution_control:
-  monitoring:
-    real_time_tracking:
-      - current_story_progress: 当前故事进度
-      - completion_percentage: 完成百分比
-      - quality_metrics: 质量指标
-      - blocking_issues: 阻塞问题
-
-    progress_reporting:
-      frequency: "continuous"
-      metrics:
-        - story_completion_status: 故事完成状态
-        - quality_gate_status: 质量门控状态
-        - estimated_completion_time: 预计完成时间
-        - risk_indicators: 风险指标
-
-  control_mechanisms:
-    blocking_prevention:
-      - dependency_validation: 依赖验证
-      - resource_availability: 资源可用性
-      - quality_compliance: 质量合规性
-
-    failure_handling:
-      - immediate_stop: 发现问题立即停止
-      - root_cause_analysis: 根因分析
-      - corrective_action: 纠正措施
-      - validation_before_continue: 继续前验证
-```
-
-## Output Specifications
-
-### 1. 串行开发计划
-
-```yaml
-# serial_development_plan.yaml
-project_execution_plan:
-  execution_mode: strict_sequential
-  total_stories: ${story_count}
-  estimated_duration: ${duration_estimate}
-
-  story_sequence:
-    - story_id: ${story_1_id}
-      priority: 1
-      dependencies: []
-      estimated_effort: ${effort_1}
-      quality_gates: [${gates_1}]
-
-    - story_id: ${story_2_id}
-      priority: 2
-      dependencies: [${story_1_id}]
-      estimated_effort: ${effort_2}
-      quality_gates: [${gates_2}]
-
-  quality_framework:
-    gate_count: ${gate_count}
-    validation_steps: ${validation_steps}
-    completion_criteria: ${criteria}
-```
-
-### 2. 执行状态仪表板
-
-```markdown
-# Serial Development Dashboard
-
-## Current Execution Status
-
-- **Current Story**: ${current_story}
-- **Progress**: ${progress_percentage}%
-- **Quality Gate**: ${current_gate_status}
-- **Estimated Completion**: ${eta}
-
-## Completed Stories
-
-${completed_stories_list}
-
-## Pending Stories Queue
-
-${pending_stories_queue}
-
-## Quality Metrics
-
-- **Code Coverage**: ${coverage}%
-- **Test Pass Rate**: ${test_pass_rate}%
-- **Quality Score**: ${quality_score}
-- **Defect Density**: ${defect_density}
-
-## Risk Indicators
-
-${risk_indicators}
-```
-
-### 3. 质量保证报告
-
-```markdown
-# Quality Assurance Report
-
-## Story-by-Story Quality Summary
-
-${story_quality_summary}
-
-## Quality Gate Results
-
-${quality_gate_results}
-
-## Integration Test Results
-
-${integration_test_results}
-
-## Final Validation Results
-
-${final_validation_results}
-```
-
-## Task Execution Context
-
-### Triggering Conditions
-
-```yaml
-triggers:
-  primary:
-    condition: story_backlog_ready
-    trigger: "*orchestrate-serial-development"
-
-  dependencies:
-    required_inputs:
-      - project_story_backlog.md: 项目故事积压清单
-      - story_dependency_graph.yaml: 故事依赖关系图
-      - development_resources.yaml: 开发资源配置
-
-    optional_inputs:
-      - quality_standards.yaml: 质量标准配置
-      - risk_thresholds.yaml: 风险阈值配置
-```
-
-### Success Criteria
-
-```yaml
-success_criteria:
-  completion:
-    - all_stories_completed: 所有故事100%完成
-    - quality_gates_passed: 所有质量门控通过
-    - integration_successful: 集成测试成功
-    - deliverable_ready: 交付物就绪
-
-  quality:
-    - code_coverage: ">=95%"
-    - test_pass_rate: "100%"
-    - defect_density: "<=0.1 per KLOC"
-    - performance_baseline: "met"
-
-  process:
-    - strict_sequence_followed: 严格按序执行
-    - no_parallel_execution: 无并行执行
-    - dependency_respect: 依赖关系遵守
-    - quality_consistency: 质量标准一致
-```
-
-### Error Handling
-
-```yaml
-error_handling:
-  blocking_issues:
-    detection:
-      - quality_gate_failure: 质量门控失败
-      - dependency_not_met: 依赖未满足
-      - resource_unavailable: 资源不可用
-
-    response:
-      - immediate_stop: 立即停止执行
-      - issue_analysis: 问题分析
-      - corrective_action: 纠正措施
-      - validation_before_resume: 恢复前验证
-
-  quality_failures:
-    test_failures:
-      action: "stop_and_fix"
-      escalation: "immediate"
-
-    coverage_below_threshold:
-      action: "stop_and_improve"
-      requirement: "meet_coverage_target"
-
-    integration_failures:
-      action: "rollback_and_debug"
-      validation: "complete_retest"
-```
-
-## Integration Points
-
-### 与 full-requirement-orchestrator 集成
-
-```yaml
-integration:
-  orchestrator_coordination:
-    command_mapping:
-      - '*orchestrate-serial-development' → serial-development-orchestration
-
-    data_exchange:
-      inputs_from_orchestrator:
-        - project_story_backlog.md
-        - story_dependency_graph.yaml
-
-      outputs_to_orchestrator:
-        - serial_development_plan.yaml
-        - execution_progress_dashboard.md
-        - quality_assurance_report.md
-
-  workflow_alignment:
-    phase_mapping:
-      - orchestrator_phase_3 → serial_development_execution
-
-    quality_sync:
-      - orchestrator_quality_gates ↔ task_quality_gates
-```
-
-## Usage Examples
-
-### 启动串行开发编排
-
-```bash
-# 激活 full-requirement-orchestrator
-*agent full-requirement-orchestrator
-
-# 启动串行开发编排
-*orchestrate-serial-development
-
-# 监控串行执行进度
-*monitor-project-progress
-```
-
-### 查看串行开发计划
-
-```bash
-# 查看生成的串行开发计划
-cat serial_development_plan.yaml
-
-# 查看执行状态仪表板
-cat execution_progress_dashboard.md
-
-# 查看质量保证报告
-cat quality_assurance_report.md
-```
-
-### 处理执行问题
-
-```bash
-# 查看当前执行状态
-*monitor-project-progress
-
-# 处理跨故事冲突
-*handle-cross-story-conflicts
-
-# 强制质量门控检查
-*execute-quality-gates
-```
-
-## Best Practices
-
-### 串行执行优化
-
-1. **严格顺序**: 绝对不允许跳过或并行执行
-2. **质量优先**: 质量门控失败时立即停止
-3. **依赖验证**: 每个故事开始前验证所有依赖
-4. **持续监控**: 实时跟踪执行状态和质量指标
-
-### 风险管理
-
-1. **早期发现**: 在问题扩散前及时发现和处理
-2. **快速响应**: 发现问题后立即停止和分析
-3. **彻底修复**: 确保问题完全解决后才继续
-4. **文档记录**: 详细记录所有问题和解决方案
-
-### 质量保证
-
-1. **全覆盖测试**: 确保所有功能都有完整测试
-2. **集成验证**: 每个故事完成后进行集成验证
-3. **性能基准**: 维护性能基准并持续监控
-4. **安全扫描**: 定期进行安全漏洞扫描
-
-这个串行开发编排任务确保了严格的顺序执行，每个任务必须100%完成并通过所有质量门控后才能开始下一个任务，完全消除了并行执行的可能性。

package/xiaoma-core/tasks/shard-doc.md

@@ -1,187 +0,0 @@
-<!-- Powered by XiaoMa™ Core -->
-
-# Document Sharding Task
-
-## Purpose
-
-- Split a large document into multiple smaller documents based on level 2 sections
-- Create a folder structure to organize the sharded documents
-- Maintain all content integrity including code blocks, diagrams, and markdown formatting
-
-## Primary Method: Automatic with markdown-tree
-
-[[LLM: First, check if markdownExploder is set to true in {root}/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
-
-If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
-
-If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
-
-1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-2. Or set markdownExploder to false in {root}/core-config.yaml
-
-**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
-
-If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
-
-1. Set markdownExploder to true in {root}/core-config.yaml
-2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-
-I will now proceed with the manual sharding process."
-
-Then proceed with the manual method below ONLY if markdownExploder is false.]]
-
-### Installation and Usage
-
-1. **Install globally**:
-
-   ```bash
-   npm install -g @kayvan/markdown-tree-parser
-   ```
-
-2. **Use the explode command**:
-
-   ```bash
-   # For PRD
-   md-tree explode docs/prd.md docs/prd
-
-   # For Architecture
-   md-tree explode docs/architecture.md docs/architecture
-
-   # For any document
-   md-tree explode [source-document] [destination-folder]
-   ```
-
-3. **What it does**:
-   - Automatically splits the document by level 2 sections
-   - Creates properly named files
-   - Adjusts heading levels appropriately
-   - Handles all edge cases with code blocks and special markdown
-
-If the user has @kayvan/markdown-tree-parser installed, use it and skip the manual process below.
-
----
-
-## Manual Method (if @kayvan/markdown-tree-parser is not available or user indicated manual method)
-
-### Task Instructions
-
-1. Identify Document and Target Location
-
-- Determine which document to shard (user-provided path)
-- Create a new folder under `docs/` with the same name as the document (without extension)
-- Example: `docs/prd.md` → create folder `docs/prd/`
-
-2. Parse and Extract Sections
-
-CRITICAL AEGNT SHARDING RULES:
-
-1. Read the entire document content
-2. Identify all level 2 sections (## headings)
-3. For each level 2 section:
-   - Extract the section heading and ALL content until the next level 2 section
-   - Include all subsections, code blocks, diagrams, lists, tables, etc.
-   - Be extremely careful with:
-     - Fenced code blocks (```) - ensure you capture the full block including closing backticks and account for potential misleading level 2's that are actually part of a fenced section example
-     - Mermaid diagrams - preserve the complete diagram syntax
-     - Nested markdown elements
-     - Multi-line content that might contain ## inside code blocks
-
-CRITICAL: Use proper parsing that understands markdown context. A ## inside a code block is NOT a section header.]]
-
-### 3. Create Individual Files
-
-For each extracted section:
-
-1. **Generate filename**: Convert the section heading to lowercase-dash-case
-   - Remove special characters
-   - Replace spaces with dashes
-   - Example: "## Tech Stack" → `tech-stack.md`
-
-2. **Adjust heading levels**:
-   - The level 2 heading becomes level 1 (# instead of ##) in the sharded new document
-   - All subsection levels decrease by 1:
-
-   ```txt
-     - ### → ##
-     - #### → ###
-     - ##### → ####
-     - etc.
-   ```
-
-3. **Write content**: Save the adjusted content to the new file
-
-### 4. Create Index File
-
-Create an `index.md` file in the sharded folder that:
-
-1. Contains the original level 1 heading and any content before the first level 2 section
-2. Lists all the sharded files with links:
-
-```markdown
-# Original Document Title
-
-[Original introduction content if any]
-
-## Sections
-
-- [Section Name 1](./section-name-1.md)
-- [Section Name 2](./section-name-2.md)
-- [Section Name 3](./section-name-3.md)
-  ...
-```
-
-### 5. Preserve Special Content
-
-1. **Code blocks**: Must capture complete blocks including:
-
-   ```language
-   content
-   ```
-
-2. **Mermaid diagrams**: Preserve complete syntax:
-
-   ```mermaid
-   graph TD
-   ...
-   ```
-
-3. **Tables**: Maintain proper markdown table formatting
-
-4. **Lists**: Preserve indentation and nesting
-
-5. **Inline code**: Preserve backticks
-
-6. **Links and references**: Keep all markdown links intact
-
-7. **Template markup**: If documents contain {{placeholders}} ,preserve exactly
-
-### 6. Validation
-
-After sharding:
-
-1. Verify all sections were extracted
-2. Check that no content was lost
-3. Ensure heading levels were properly adjusted
-4. Confirm all files were created successfully
-
-### 7. Report Results
-
-Provide a summary:
-
-```text
-Document sharded successfully:
-- Source: [original document path]
-- Destination: docs/[folder-name]/
-- Files created: [count]
-- Sections:
-  - section-name-1.md: "Section Title 1"
-  - section-name-2.md: "Section Title 2"
-  ...
-```
-
-## Important Notes
-
-- Never modify the actual content, only adjust heading levels
-- Preserve ALL formatting, including whitespace where significant
-- Handle edge cases like sections with code blocks containing ## symbols
-- Ensure the sharding is reversible (could reconstruct the original from shards)