@zeyue0329/xiaoma-cli 1.0.49 → 1.6.4

package/xiaoma-core/templates/requirements-coverage-audit.yaml

@@ -1,330 +0,0 @@
-# Requirements Coverage Audit Task
-# 需求覆盖度审计任务
-
-meta:
-  name: "Requirements Coverage Audit"
-  description: "全面检查产品需求到用户故事的转化完整性和实施状态"
-  version: "1.0"
-  created_date: "2025-09-10"
-  tags: ["audit", "requirements", "coverage", "validation"]
-
-# ========== 任务配置 ==========
-task:
-  name: "requirements-coverage-audit"
-  aliases:
-    - "coverage-audit"
-    - "requirement-check"
-    - "story-validation"
-  category: "validation"
-  complexity: "medium"
-  estimated_duration: "20-30 minutes"
-
-# ========== 任务描述 ==========
-description: |
-  系统性检查和验证：
-
-  📋 **需求转化检查**:
-  - PRD文档需求是否完全转化为用户故事
-  - 模块级需求的用户故事覆盖度
-  - 需求优先级和实施状态匹配度
-
-  ✅ **用户故事完整性检查**:
-  - 用户故事是否包含完整的验收标准
-  - 数据库设计是否完整实施
-  - API接口是否完全实现
-  - 任务分解是否合理且完成
-
-  🎯 **实施状态验证**:
-  - 用户故事状态的准确性
-  - 开发任务的完成度
-  - QA结果的真实性
-  - 交付物的完整性
-
-# ========== 执行流程 ==========
-execution:
-  # 第一阶段：需求源文档分析
-  phase_1_requirement_analysis:
-    name: "需求源文档分析"
-    duration: "5-8分钟"
-    steps:
-      - step: "load_prd_documents"
-        description: "加载PRD文档"
-        actions:
-          - "读取主PRD文档"
-          - "扫描docs/prd/目录下的模块文件"
-          - "提取所有需求和用户故事定义"
-          - "构建需求层次结构"
-        output: "requirements_inventory.json"
-
-      - step: "extract_requirements_matrix"
-        description: "提取需求矩阵"
-        actions:
-          - "识别所有模块和用户故事"
-          - "提取验收标准和功能点"
-          - "分析需求优先级"
-          - "构建需求依赖关系"
-        output: "requirements_matrix.json"
-
-  # 第二阶段：用户故事实施分析
-  phase_2_story_implementation_analysis:
-    name: "用户故事实施分析"
-    duration: "8-12分钟"
-    steps:
-      - step: "scan_implemented_stories"
-        description: "扫描已实施用户故事"
-        actions:
-          - "扫描docs/stories/目录"
-          - "解析每个用户故事文档"
-          - "提取实施状态和完成度"
-          - "分析任务完成情况"
-        output: "implemented_stories_inventory.json"
-
-      - step: "analyze_story_completeness"
-        description: "分析用户故事完整性"
-        actions:
-          - "检查必需章节完整性"
-          - "验证数据库设计实施"
-          - "检查API接口实现"
-          - "分析任务分解和完成度"
-        output: "story_completeness_report.json"
-
-  # 第三阶段：覆盖度映射和差距分析
-  phase_3_coverage_gap_analysis:
-    name: "覆盖度映射和差距分析"
-    duration: "5-8分钟"
-    steps:
-      - step: "map_requirements_to_stories"
-        description: "需求到故事映射"
-        actions:
-          - "建立需求-用户故事映射关系"
-          - "识别已实施的需求"
-          - "识别未实施的需求"
-          - "分析实施覆盖度"
-        output: "coverage_mapping.json"
-
-      - step: "identify_gaps_and_issues"
-        description: "识别差距和问题"
-        actions:
-          - "识别需求覆盖差距"
-          - "发现不一致的实施状态"
-          - "分析质量问题"
-          - "生成改进建议"
-        output: "gaps_and_issues_report.json"
-
-  # 第四阶段：生成综合审计报告
-  phase_4_comprehensive_reporting:
-    name: "生成综合审计报告"
-    duration: "2-5分钟"
-    steps:
-      - step: "generate_coverage_report"
-        description: "生成覆盖度报告"
-        actions:
-          - "计算整体覆盖度指标"
-          - "生成需求实施矩阵"
-          - "创建可视化图表"
-          - "提供详细分析"
-        output: "requirements_coverage_report.md"
-
-      - step: "generate_action_plan"
-        description: "生成行动计划"
-        actions:
-          - "优先级排序未实施需求"
-          - "制定实施路线图"
-          - "生成具体行动项"
-          - "估算工作量"
-        output: "implementation_action_plan.md"
-
-# ========== 检查维度定义 ==========
-audit_dimensions:
-  # 维度1：需求覆盖度
-  requirement_coverage:
-    name: "需求覆盖度分析"
-    metrics:
-      - "总需求数量"
-      - "已转化为用户故事的需求数量"
-      - "覆盖度百分比"
-      - "未覆盖需求清单"
-    acceptance_criteria:
-      minimum_coverage: 85 # 最低覆盖度85%
-      critical_requirements_coverage: 100 # 关键需求100%覆盖
-
-  # 维度2：用户故事完整性
-  story_completeness:
-    name: "用户故事完整性分析"
-    checks:
-      - "必需章节完整性"
-      - "验收标准明确性"
-      - "数据库设计完整性"
-      - "API接口规范完整性"
-      - "任务分解合理性"
-    scoring:
-      structure_completeness: 30 # 结构完整性权重30%
-      content_quality: 40 # 内容质量权重40%
-      implementation_detail: 30 # 实施细节权重30%
-
-  # 维度3：实施状态准确性
-  implementation_accuracy:
-    name: "实施状态准确性验证"
-    validations:
-      - "状态声明与实际内容匹配度"
-      - "QA结果的真实性"
-      - "开发者记录的完整性"
-      - "交付物的存在性"
-    verification_methods:
-      - "文档结构验证"
-      - "内容完整性检查"
-      - "实施证据验证"
-      - "质量标准符合度"
-
-  # 维度4：业务价值实现
-  business_value_realization:
-    name: "业务价值实现分析"
-    assessments:
-      - "关键功能实施状态"
-      - "用户价值主张实现度"
-      - "业务目标达成情况"
-      - "ROI预期实现度"
-    priority_analysis:
-      - "高优先级需求实施率"
-      - "核心功能完成度"
-      - "用户体验改善程度"
-
-# ========== 报告结构定义 ==========
-report_structure:
-  # 执行摘要
-  executive_summary:
-    sections:
-      - "整体覆盖度概述"
-      - "关键发现和问题"
-      - "优先改进建议"
-      - "实施状态评级"
-
-  # 详细分析
-  detailed_analysis:
-    sections:
-      - requirements_coverage_matrix:
-          title: "需求覆盖度矩阵"
-          content: "模块-用户故事映射表"
-      - story_completeness_analysis:
-          title: "用户故事完整性分析"
-          content: "每个故事的完整性评分"
-      - implementation_status_review:
-          title: "实施状态审查"
-          content: "实施声明的验证结果"
-      - gap_analysis:
-          title: "差距分析"
-          content: "未实施需求和改进机会"
-
-  # 行动计划
-  action_plan:
-    sections:
-      - "立即行动项"
-      - "短期改进计划"
-      - "长期完善建议"
-      - "资源需求评估"
-
-# ========== 质量检查规则 ==========
-quality_check_rules:
-  # 用户故事必需元素检查
-  required_story_elements:
-    - element: "用户故事格式"
-      pattern: "^\\*\\*作为\\*\\*.*\\*\\*我希望\\*\\*.*\\*\\*以便\\*\\*.*"
-      criticality: "HIGH"
-
-    - element: "验收标准"
-      minimum_count: 3
-      format: "numbered_list"
-      criticality: "HIGH"
-
-    - element: "数据库设计相关"
-      required_subsections: ["涉及的数据库实体", "数据操作清单", "业务规则约束"]
-      criticality: "MEDIUM"
-
-    - element: "API接口规范"
-      required_subsections: ["API端点清单", "API详细设计", "数据映射关系"]
-      criticality: "HIGH"
-
-    - element: "开发者代理记录"
-      required_subsections:
-        ["使用的代理模型", "数据库实现记录", "API实现记录", "文件列表"]
-      criticality: "LOW"
-
-  # 实施状态验证规则
-  implementation_status_rules:
-    - status: "Completed"
-      required_evidence:
-        - "QA结果章节存在且非空"
-        - "开发者代理记录完整"
-        - "文件列表非空"
-        - "所有验收标准有对应实施"
-
-    - status: "InProgress"
-      required_evidence:
-        - "部分验收标准有实施记录"
-        - "开发者代理记录存在"
-
-    - status: "Draft"
-      required_evidence:
-        - "基本结构完整"
-
-# ========== 输出格式 ==========
-output_formats:
-  # 主要报告
-  primary_reports:
-    - name: "requirements_coverage_audit_report"
-      location: "audit-reports/"
-      format: "COMPREHENSIVE_MARKDOWN"
-      includes: ["executive_summary", "detailed_analysis", "recommendations"]
-
-    - name: "implementation_gap_analysis"
-      location: "audit-reports/"
-      format: "STRUCTURED_MARKDOWN"
-      includes: ["gap_matrix", "priority_ranking", "action_items"]
-
-  # 数据文件
-  data_exports:
-    - name: "requirements_matrix"
-      format: "JSON"
-      description: "结构化需求映射数据"
-
-    - name: "coverage_metrics"
-      format: "JSON"
-      description: "覆盖度指标数据"
-
-    - name: "story_completeness_scores"
-      format: "JSON"
-      description: "用户故事完整性评分"
-
-# ========== 成功标准 ==========
-success_criteria:
-  audit_completeness:
-    - "所有PRD需求识别和分类"
-    - "所有用户故事完整性评估"
-    - "覆盖度映射100%完成"
-    - "差距分析全面准确"
-
-  report_quality:
-    - "执行摘要清晰简明"
-    - "分析数据准确可靠"
-    - "改进建议具体可行"
-    - "行动计划优先级明确"
-
-  actionable_insights:
-    - "识别具体的覆盖度差距"
-    - "提供可执行的改进建议"
-    - "制定合理的实施时间表"
-    - "估算准确的工作量"
-
-# ========== 使用示例 ==========
-usage_examples:
-  basic_audit: |
-    # 执行完整的需求覆盖度审计
-    *requirements-coverage-audit
-
-  focused_audit: |
-    # 专注于特定模块的审计
-    *coverage-audit --epic=模块-1基础设施与核心文档展示
-
-  status_verification: |
-    # 验证用户故事状态准确性
-    *story-validation --focus=implementation-status

package/xiaoma-core/templates/start-enhanced-workflow.yaml

@@ -1,347 +0,0 @@
-# Start Enhanced Workflow Task
-# 启动增强工作流任务
-
-meta:
-  name: "Start Enhanced Workflow"
-  description: "启动全流程自动化增强工作流系统"
-  version: "2.0"
-  created_date: "2025-09-10"
-  tags: ["workflow", "automation", "quality"]
-
-# ========== 任务配置 ==========
-task:
-  name: "start-enhanced-workflow"
-  aliases:
-    - "enhanced-workflow"
-    - "start-full-quality-automation"
-    - "activate-enhanced-system"
-  category: "automation"
-  complexity: "high"
-  estimated_duration: "60-120 minutes"
-
-# ========== 任务描述 ==========
-description: |
-  启动基于多层质量保证的增强工作流系统（严格串行执行模式）。该系统提供：
-
-  🎯 **核心功能**:
-  - 全流程自动化文档处理
-  - 7层质量验证系统
-  - 智能模板理解和适配
-  - 自动错误检测和纠正
-  - 实时进度监控和报告
-
-  🛡️ **质量保证**:
-  - 语法格式验证 (100%通过率)
-  - 内容完整性验证 (≥90%标准)
-  - 内容质量验证 (≥87%标准)
-  - 一致性验证 (≥96%标准)
-  - 实施可行性验证 (≥83%标准)
-  - 业务价值验证 (≥82%标准)
-  - 最终集成验证 (≥90%标准)
-
-  ⚡ **执行特性**:
-  - 严格串行执行模式
-  - 依赖关系强制验证
-  - 100%完成度要求
-  - 自动纠错机制
-  - 回滚和恢复能力
-  - 零容错质量标准
-
-# ========== 执行流程 ==========
-execution:
-  # 前置检查
-  pre_checks:
-    - check_system_requirements
-    - validate_project_structure
-    - verify_template_accessibility
-    - confirm_write_permissions
-
-  # 主要执行步骤
-  main_steps:
-    - step: "system_initialization"
-      description: "系统初始化"
-      agent: "master-execution-engine"
-      timeout: 600
-      actions:
-        - "加载项目上下文"
-        - "初始化质量验证系统"
-        - "验证模板理解能力"
-        - "设置质量门控"
-      success_criteria:
-        - "所有系统组件正常"
-        - "模板理解验证通过"
-        - "质量系统就绪"
-
-    - step: "intelligent_planning"
-      description: "智能任务规划"
-      agent: "enhanced-workflow-orchestrator"
-      timeout: 900
-      actions:
-        - "分析项目范围和需求"
-        - "识别任务依赖关系"
-        - "优化执行策略"
-        - "配置并行处理"
-      success_criteria:
-        - "任务分析完成"
-        - "执行策略优化"
-        - "质量保证规划就绪"
-
-    - step: "template_adaptation"
-      description: "模板智能适配"
-      agent: "intelligent-template-adapter"
-      timeout: 600
-      actions:
-        - "深度理解模板结构"
-        - "验证模板理解正确性"
-        - "准备内容生成引擎"
-        - "配置质量检查规则"
-      success_criteria:
-        - "模板理解100%准确"
-        - "内容生成引擎就绪"
-        - "质量规则配置完成"
-
-    - step: "batch_processing"
-      description: "批量文档处理"
-      agent: "automated-quality-validator"
-      timeout: 2400
-      parallel: true
-      batch_size: 3
-      actions:
-        - "执行7层质量验证"
-        - "自动内容生成和增强"
-        - "实时错误检测和纠正"
-        - "生成质量报告"
-      success_criteria:
-        - "所有质量层验证通过"
-        - "文档格式完全合规"
-        - "内容质量达标"
-
-    - step: "integration_validation"
-      description: "集成验证"
-      agent: "master-execution-engine"
-      timeout: 1500
-      actions:
-        - "跨文档一致性验证"
-        - "全局质量评估"
-        - "集成测试执行"
-        - "最终质量认证"
-      success_criteria:
-        - "全局一致性达标"
-        - "集成测试通过"
-        - "质量认证颁发"
-
-    - step: "delivery_preparation"
-      description: "交付准备"
-      agent: "master-execution-engine"
-      timeout: 900
-      actions:
-        - "生成综合报告"
-        - "准备交付包"
-        - "更新项目文档"
-        - "完成质量认证"
-      success_criteria:
-        - "交付包完整"
-        - "质量认证完成"
-        - "实施就绪确认"
-
-# ========== 质量门控 ==========
-quality_gates:
-  gate_1_system_ready:
-    name: "系统就绪验证"
-    criteria:
-      - "all_components_operational"
-      - "template_understanding_verified"
-      - "quality_system_initialized"
-    failure_action: "ABORT_WITH_DIAGNOSTICS"
-
-  gate_2_planning_complete:
-    name: "规划完成验证"
-    criteria:
-      - "task_analysis_validated"
-      - "strategy_feasibility_confirmed"
-      - "qa_readiness_validated"
-    failure_action: "REPLANNING_CYCLE"
-
-  gate_3_template_ready:
-    name: "模板就绪验证"
-    criteria:
-      - "template_comprehension_100_percent"
-      - "content_generation_engine_ready"
-      - "quality_rules_configured"
-    failure_action: "TEMPLATE_RE_ANALYSIS"
-
-  gate_4_quality_validation:
-    name: "质量验证通过"
-    criteria:
-      - "all_7_layers_passed"
-      - "quality_scores_meet_thresholds"
-      - "zero_critical_errors"
-    failure_action: "ITERATIVE_IMPROVEMENT"
-
-  gate_5_integration_success:
-    name: "集成验证成功"
-    criteria:
-      - "global_consistency_achieved"
-      - "integration_tests_passed"
-      - "delivery_readiness_confirmed"
-    failure_action: "COMPREHENSIVE_REFINEMENT"
-
-# ========== 错误处理 ==========
-error_handling:
-  error_categories:
-    critical_errors:
-      items:
-        - "system_initialization_failure"
-        - "template_understanding_failure"
-        - "quality_gate_critical_failure"
-      actions: "IMMEDIATE_STOP_AND_REPORT"
-
-    recoverable_errors:
-      items:
-        - "quality_threshold_not_met"
-        - "content_completeness_issues"
-        - "consistency_problems"
-      actions: "AUTO_CORRECTION_CYCLE"
-
-    warning_conditions:
-      items:
-        - "performance_degradation"
-        - "resource_constraints"
-        - "timeout_approaching"
-      actions: "LOG_AND_CONTINUE_WITH_MONITORING"
-
-  recovery_strategies:
-    - "checkpoint_rollback"
-    - "selective_retry"
-    - "alternative_path_execution"
-    - "graceful_degradation"
-
-# ========== 输出规范 ==========
-output_specification:
-  primary_outputs:
-    - name: "enhanced_user_stories"
-      location: "docs/stories/"
-      format: "ENHANCED_MARKDOWN"
-      description: "增强格式的用户故事文档"
-
-    - name: "quality_certification_report"
-      location: "reports/quality/"
-      format: "MARKDOWN_WITH_METRICS"
-      description: "全面的质量认证报告"
-
-    - name: "implementation_readiness_certificate"
-      location: "certificates/"
-      format: "STRUCTURED_DOCUMENT"
-      description: "实施就绪认证书"
-
-  secondary_outputs:
-    - name: "execution_log"
-      location: "logs/"
-      format: "STRUCTURED_LOG"
-      description: "详细的执行日志"
-
-    - name: "performance_metrics"
-      location: "metrics/"
-      format: "JSON"
-      description: "性能指标数据"
-
-    - name: "improvement_recommendations"
-      location: "recommendations/"
-      format: "MARKDOWN"
-      description: "持续改进建议"
-
-# ========== 用户交互 ==========
-user_interaction:
-  interaction_points:
-    pre_execution:
-      - confirm_execution_mode
-      - review_quality_thresholds
-      - approve_batch_configuration
-
-    during_execution:
-      - display_real_time_progress
-      - show_quality_gate_status
-      - alert_on_critical_issues
-
-    post_execution:
-      - present_quality_summary
-      - confirm_delivery_acceptance
-      - provide_improvement_recommendations
-
-  customization_options:
-    execution_mode:
-      options: ["MAXIMUM_QUALITY", "BALANCED_EFFICIENCY", "RAPID_DELIVERY"]
-      default: "MAXIMUM_QUALITY"
-      description: "选择执行模式以平衡质量和效率"
-
-    batch_size:
-      options: [1, 3, 5]
-      default: 3
-      description: "设置并行处理批次大小"
-
-    quality_thresholds:
-      adjustable: true
-      min_values:
-        overall_quality: 80
-        template_compliance: 100
-        content_completeness: 80
-      default_values:
-        overall_quality: 90
-        template_compliance: 100
-        content_completeness: 90
-
-# ========== 成功标准 ==========
-success_criteria:
-  mandatory_requirements:
-    - "all_quality_gates_passed"
-    - "zero_critical_errors"
-    - "template_compliance_100_percent"
-    - "implementation_readiness_achieved"
-
-  quality_thresholds:
-    overall_quality_score: 90
-    template_compliance_rate: 100
-    content_completeness_rate: 90
-    consistency_score: 95
-    implementation_feasibility_score: 85
-    business_value_alignment_score: 80
-
-  deliverable_requirements:
-    - "all_user_stories_enhanced"
-    - "quality_certification_issued"
-    - "implementation_guide_complete"
-    - "continuous_improvement_plan_provided"
-
-# ========== 使用示例 ==========
-usage_examples:
-  basic_usage: |
-    # 启动增强工作流
-    *start-enhanced-workflow
-
-  with_options: |
-    # 使用自定义配置启动
-    *start-enhanced-workflow --mode=MAXIMUM_QUALITY --batch-size=3 --parallel=true
-
-  quick_start: |
-    # 快速启动（使用默认配置）
-    *enhanced-workflow
-
-# ========== 预期效果 ==========
-expected_outcomes:
-  quality_improvements:
-    - "零格式错误和结构缺陷"
-    - "90%以上的整体质量分数"
-    - "100%的模板合规性"
-    - "95%以上的跨文档一致性"
-
-  efficiency_gains:
-    - "99%的自动化处理率"
-    - "减少90%的人工返工需求"
-    - "提高60%的文档处理速度"
-    - "实现全程可视化监控"
-
-  business_value:
-    - "开发就绪的交付成果"
-    - "完整的质量认证文档"
-    - "详细的实施指导"
-    - "持续改进建议"