@chongyan/autospec 1.0.2 → 1.0.4

package/knowledge/05-config/03-role-composition.yaml

@@ -1,346 +0,0 @@
-# ============================================
-# 角色组合配置（AI Native团队阵型）
-# 模型根据以下配置动态组织阵型
-# ============================================
-
-# ---------- 1. 复杂度阈值 ----------
-complexity_threshold:
-  simple: 5      # ≤5: 简单任务
-  medium: 8      # 6-8: 中等任务
-  complex: 9     # ≥9: 复杂任务
-
-# ---------- 2. 角色组合（按阶段+复杂度） ----------
-compositions:
-  requirement:
-    simple:
-      roles: [product-owner]
-      focus: [商业价值, 用户价值]
-      aiNative: "评估AI能力边界"
-    medium:
-      roles: [ceo, product-owner, tech-lead]
-      focus: [商业价值, 用户价值, 技术可行性]
-      aiNative: "评估AI方案可行性"
-    complex:
-      roles: [ceo, product-owner, tech-lead, ai-engineer, backend-engineer, frontend-engineer]
-      focus: [商业价值, 用户价值, 技术可行性, AI方案, 实现复杂度]
-      aiNative: "全面评估AI集成方案，制定效果评测计划"
-
-  design:
-    simple:
-      roles: [tech-lead]
-      focus: [架构设计, 技术选型]
-      aiNative: "评估AI技术选型"
-    medium:
-      roles: [tech-lead, ai-engineer, backend-engineer, frontend-engineer]
-      focus: [架构设计, 技术选型, AI方案设计, 接口设计]
-      aiNative: "AI工程师参与核心方案设计"
-    complex:
-      roles: [tech-lead, ai-engineer, data-engineer, backend-engineer, frontend-engineer, quality-engineer]
-      focus: [架构设计, 技术选型, AI方案设计, 数据架构, 接口设计, 测试策略]
-      aiNative: "设计AI效果评测方案，规划数据流"
-
-  implementation:
-    simple:
-      roles: [backend-engineer]
-      focus: [代码实现, 单元测试]
-      aiNative: "实现AI接口调用"
-    medium:
-      roles: [backend-engineer, frontend-engineer, ai-engineer]
-      focus: [代码实现, 接口对接, AI集成, 单元测试]
-      aiNative: "AI工程师负责AI模块实现"
-    complex:
-      roles: [backend-engineer, frontend-engineer, ai-engineer, data-engineer, quality-engineer]
-      focus: [代码实现, 接口对接, AI实现, 数据管道, 测试覆盖]
-      aiNative: "AI效果评测实现，数据驱动验证"
-
-  testing:
-    simple:
-      roles: [quality-engineer]
-      focus: [测试执行, 缺陷报告]
-      aiNative: "AI功能测试"
-    medium:
-      roles: [quality-engineer, backend-engineer, ai-engineer]
-      focus: [测试执行, 接口测试, AI效果评测]
-      aiNative: "AI效果评测，Badcase分析"
-    complex:
-      roles: [quality-engineer, ai-engineer, data-engineer, backend-engineer, frontend-engineer]
-      focus: [测试执行, AI效果评测, 数据验证, 集成测试]
-      aiNative: "全面AI效果评测，数据驱动验证"
-
-  delivery:
-    simple:
-      roles: [tech-lead, quality-engineer]
-      focus: [发布检查, 部署验证]
-      aiNative: "AI服务部署检查"
-    medium:
-      roles: [tech-lead, quality-engineer, devops-engineer, ai-engineer]
-      focus: [发布检查, 部署配置, AI服务部署]
-      aiNative: "AI模型部署，服务监控配置"
-    complex:
-      roles: [tech-lead, quality-engineer, devops-engineer, ai-engineer, data-engineer, security-engineer]
-      focus: [发布检查, 部署配置, AI服务部署, 数据管道, 安全检查]
-      aiNative: "AI服务全面部署，安全合规检查"
-
-# ---------- 3. 核心原则 ----------
-principles:
-  - name: "做审分离"
-    description: "执行者与审查者信息隔离，只传递必要信息"
-  - name: "级联验证"
-    description: "Layer 1(编译/测试)不过，不进Layer 2(AI审查)"
-  - name: "Human-on-the-loop"
-    description: "关键决策人工确认，不可逆动作必须人工授权"
-  - name: "精准回退"
-    description: "3次修复失败升级人工，避免无限循环"
-  - name: "模板即约束"
-    description: "产出模板含强制字段、不确定性标记、自检清单，让AI很难生成坏的产出"
-  - name: "跨产物一致性"
-    description: "阶段完成后自动检测重复/歧义/规格不全/宪法对齐/覆盖缺口/术语漂移"
-  - name: "任务拆解"
-    description: "多系统/大规模任务按Phase拆Task(2-4h)，解耦并行，串行不跳过"
-  - name: "安全制动"
-    description: "不可逆动作人工确认，安全风险立即停止"
-
-# ---------- 4. 动态决策树 ----------
-decision_tree:
-  # 项目特征 -> 角色（根据项目实际情况动态添加）
-  rules:
-    - condition: "涉及AI/ML功能"
-      action: "add"
-      roles: [ai-engineer]
-    - condition: "涉及数据管道/数据仓库/ML数据处理"
-      action: "add"
-      roles: [data-engineer]
-    - condition: "涉及用户数据/支付/身份认证"
-      action: "add"
-      roles: [security-engineer]
-    - condition: "涉及前端开发"
-      action: "add"
-      roles: [frontend-engineer]
-    - condition: "涉及后端开发"
-      action: "add"
-      roles: [backend-engineer]
-    - condition: "需要全栈能力"
-      action: "use"
-      roles: [fullstack-engineer]
-      instead_of: [backend-engineer, frontend-engineer]
-    - condition: "涉及部署/基础设施"
-      action: "add"
-      roles: [devops-engineer]
-    - condition: "有高性能/低延迟要求"
-      action: "add"
-      roles: [performance-engineer]
-    - condition: "涉及用户界面/用户体验"
-      action: "add"
-      roles: [ux-designer]
-
-  # 复杂度 -> 角色数量
-  complexity_rules:
-    - condition: "simple (<=5)"
-      min_roles: 1
-      max_roles: 2
-    - condition: "medium (6-8)"
-      min_roles: 2
-      max_roles: 4
-    - condition: "complex (>=9)"
-      min_roles: 4
-      max_roles: 6
-
-  # 强制触发（不可跳过）
-  mandatory:
-    - condition: "涉及用户数据"
-      must_add: [security-engineer]
-    - condition: "涉及支付/资金"
-      must_add: [security-engineer]
-    - condition: "涉及身份认证"
-      must_add: [security-engineer]
-    - condition: "涉及AI功能"
-      must_add: [ai-engineer]
-    - condition: "涉及数据分析/报表"
-      must_add: [data-engineer]
-    - condition: "涉及数据管道/ETL"
-      must_add: [data-engineer, devops-engineer]
-    - condition: "涉及AI效果评测"
-      must_add: [ai-engineer, quality-engineer]
-    - condition: "交付归档阶段"
-      must_run: [consistency-checker]
-    - condition: "修复失败3次"
-      must_run: [failure-diagnostician]
-    - condition: "阶段完成"
-      must_run: [stage-gate-evaluator]
-
-# ---------- 5. 效率优化 ----------
-optimization:
-  # 并行审查（默认开启）
-  parallel_review:
-    enabled: true
-    description: "多角色并行审查，总时间=最长角色时间"
-
-  # 增量审查
-  incremental_review:
-    enabled: true
-    requires_version_tag: false
-    min_similarity: 0.8
-    description: "文档有变更时只审查变更部分"
-
-  # 快速模式（条件触发）
-  fast_mode:
-    enabled: true
-    conditions:
-      - "复杂度 ≤ 3"
-      - "无安全敏感内容"
-      - "历史成功率 > 80%"
-    description: "满足条件时可减少角色数量"
-
-  # 跳过记录（可追溯）
-  skip_log:
-    enabled: true
-    description: "记录所有跳过及理由，便于追溯和审计"
-
-# ---------- 6. 安全制动 ----------
-safety_brake:
-  # 不可逆动作 → 人工确认
-  require_human_confirm:
-    - action: "数据库迁移"
-    - action: "生产环境部署"
-    - action: "外部API调用"
-    - action: "删除数据"
-    - action: "权限变更"
-
-  # 高风险 → 立即停止
-  immediate_stop:
-    - condition: "安全漏洞"
-    - condition: "数据丢失风险"
-    - condition: "3次修复失败"
-
-# ---------- 7. 协作模式 ----------
-collaborationModes:
-  parallel-review:
-    description: "多角色并行审查，信息隔离"
-    execution: "parallel"
-    isolation: true
-
-  sequential-confirm:
-    description: "按顺序确认，下一角色基于上一结果"
-    execution: "sequential"
-    isolation: false
-
-  collaborative-discussion:
-    description: "多角色共同讨论，达成共识"
-    execution: "collaborative"
-    isolation: false
-
-# ---------- 8. 角色约束 ----------
-constraints:
-  # 互斥角色（不能同时担任）
-  conflicts:
-    - [independent-reviewer, backend-engineer]
-    - [independent-reviewer, frontend-engineer]
-    - [stage-gate-evaluator, tech-lead]
-
-  # 依赖角色（需要先有）
-  requires:
-    ai-engineer: [tech-lead]
-    security-engineer: [tech-lead]
-    devops-engineer: [tech-lead]
-
-# ---------- 9. 模板约束 ----------
-template_constraints:
-  enabled: true
-  rules:
-    - "产出物必须包含强制字段：结论、证据、建议"
-    - "不确定性必须明确标记为 [待确认] 或 [不确定]"
-    - "必须包含嵌入式自检清单"
-    - "预防优于检测：让AI很难生成坏的产出"
-
-# ---------- 10. 跨产物一致性 ----------
-cross_product_consistency:
-  enabled: true
-  dimensions:
-    - name: "重复"
-      description: "检测需求/设计/代码中的重复内容"
-    - name: "歧义"
-      description: "检测描述不一致"
-    - name: "规格不全"
-      description: "检测缺失的规格说明"
-    - name: "宪法对齐"
-      description: "检测与核心原则的冲突"
-    - name: "覆盖缺口"
-      description: "检测测试覆盖不足"
-    - name: "术语漂移"
-      description: "检测术语使用不一致"
-  trigger: "每个阶段完成后自动检查"
-
-# ---------- 11. 任务拆解 ----------
-task_breakdown:
-  triggers:
-    - condition: "多子系统项目（系统边界）"
-    - condition: "任务规模 > 16小时"
-    - condition: "有明确阶段依赖"
-  strategy:
-    - "先按系统拆 Phase"
-    - "Phase 内按功能拆 Task（每任务 2-4小时）"
-  dependencies:
-    - type: "data"
-      symbol: "->data"
-      description: "数据依赖"
-    - type: "logic"
-      symbol: "->logic"
-      description: "逻辑依赖"
-    - type: "res"
-      symbol: "->res"
-      description: "资源依赖"
-  parallel:
-    - type: "contract"
-      symbol: "->contract"
-      description: "通过API契约解耦并行"
-    - type: "mock"
-      symbol: "->mock"
-      description: "通过Mock并行"
-  sequential:
-    - "数据库迁移"
-    - "核心业务流程"
-    - "AI效果验证"
-
-# ---------- 12. 执行模式 ----------
-execution_modes:
-  autonomous:
-    description: "全流程自动运行"
-    human_intervention: "仅异常/宪法/方向决策"
-  interactive:
-    description: "分阶段执行"
-    human_intervention: "每阶段确认"
-
-# ---------- 13. 团队阶段配置 ----------
-team_stages:
-  seed:
-    description: "种子期团队，精简核心角色"
-    roles: [ceo, product-owner, tech-lead]
-  growth:
-    description: "成长期团队，完整角色配置"
-    roles: [ceo, product-owner, tech-lead, backend-engineer, frontend-engineer, ai-engineer, quality-engineer]
-  mature:
-    description: "成熟期团队，专业化分工"
-    roles: [ceo, product-owner, tech-lead, backend-engineer, frontend-engineer, ai-engineer, data-engineer, quality-engineer, security-engineer, devops-engineer]
-
-# ---------- 14. 版本信息 ----------
-version: "2.0.0"
-last_updated: "2026-03-28"
-description: "融合业界精髓与原有设计的团队阵型配置"
-
-# ---------- 15. 强制执行规则 ----------
-mandatory_enforcement:
-  team_orchestrator:
-    requirement: true      # 需求阶段强制执行
-    design: true           # 设计阶段强制执行
-    implementation: true   # 实现阶段强制执行
-    skip_conditions: []    # 无跳过条件
-
-  reason: |
-    团队对抗审查是质量保障的核心机制，跳过将导致：
-    - 需求漏洞未被发现
-    - 设计缺陷未被质疑
-    - 代码风险未被识别
-
-  enforcement_rule: |
-    所有任务（包括简单任务）都必须执行团队对抗审查。
-    简单任务可使用最小团队配置，但不可跳过审查。

package/knowledge/05-config/04-role-extensions.yaml

@@ -1,140 +0,0 @@
-# 角色扩展配置
-# 定义角色的继承和扩展规则
-
-# 角色扩展定义
-extensions:
-  # 后端工程师扩展为全栈工程师
-  fullstack-engineer:
-    extends: backend-engineer
-    description: "全栈工程师，具备前后端开发能力"
-    additions:
-      tools: []
-      focus:
-        - 前端组件开发
-        - 前后端联调
-        - 全栈架构设计
-      checks:
-        - 前端性能优化
-        - 响应式设计
-        - API契约一致性
-    aiNative: "全栈AI集成，前后端AI交互优化"
-
-  # 技术负责人扩展为架构师
-  architect:
-    extends: tech-lead
-    description: "系统架构师，负责整体架构演进"
-    additions:
-      tools: []
-      focus:
-        - 系统架构演进
-        - 技术债务管理
-        - 技术规范制定
-        - 架构评审
-      checks:
-        - 架构一致性
-        - 技术选型合理性
-        - 系统可扩展性
-    aiNative: "AI架构设计，AI系统演进规划"
-
-  # AI工程师扩展为AI架构师
-  ai-architect:
-    extends: ai-engineer
-    description: "AI架构师，负责AI系统整体设计"
-    additions:
-      tools: []
-      focus:
-        - AI系统架构设计
-        - 模型选型与评估
-        - AI平台规划
-        - AI团队能力建设
-      checks:
-        - AI系统可扩展性
-        - 模型效果保障
-        - AI成本优化
-    aiNative: "AI系统架构核心设计"
-
-  # 数据工程师扩展为数据架构师
-  data-architect:
-    extends: data-engineer
-    description: "数据架构师，负责数据平台设计"
-    additions:
-      tools: []
-      focus:
-        - 数据平台架构
-        - 数据治理
-        - 数据资产建设
-      checks:
-        - 数据质量保障
-        - 数据安全合规
-        - 数据价值挖掘
-    aiNative: "AI数据架构设计，特征平台建设"
-
-  # 质量工程师扩展为测试架构师
-  test-architect:
-    extends: quality-engineer
-    description: "测试架构师，负责测试体系设计"
-    additions:
-      tools: []
-      focus:
-        - 测试体系设计
-        - 测试工具建设
-        - 质量度量体系
-      checks:
-        - 测试覆盖率
-        - 自动化测试效果
-        - 质量指标达成
-    aiNative: "AI测试架构设计，AI效果评测体系"
-
-# 角色能力提供
-provides:
-  backend-engineer:
-    - backend-api-design
-    - database-design
-    - service-implementation
-
-  frontend-engineer:
-    - ui-implementation
-    - user-interaction
-    - frontend-performance
-
-  ai-engineer:
-    - model-selection
-    - prompt-engineering
-    - ai-integration
-    - ai-evaluation
-
-  data-engineer:
-    - data-pipeline
-    - data-quality
-    - feature-engineering
-
-  quality-engineer:
-    - test-design
-    - test-automation
-    - quality-metrics
-
-  security-engineer:
-    - security-audit
-    - compliance-check
-    - vulnerability-scan
-
-# 角色组合约束
-constraints:
-  # 互斥角色（不能同时担任）
-  conflicts:
-    - [independent-reviewer, backend-engineer]
-    - [independent-reviewer, frontend-engineer]
-    - [stage-gate-evaluator, tech-lead]
-
-  # 依赖角色（需要先有）
-  requires:
-    ai-engineer: [tech-lead]
-    security-engineer: [tech-lead]
-    devops-engineer: [tech-lead]
-
-# 角色扩展规则
-rules:
-  - "扩展角色继承基础角色的所有能力"
-  - "扩展角色可以覆盖基础角色的部分定义"
-  - "扩展角色不能与基础角色冲突"
-  - "一个角色只能继承一个基础角色"

package/knowledge/05-config/05-skill-compositions.yaml

@@ -1,142 +0,0 @@
-# Skills 组合复用配置
-# 定义 Skills 的组合规则和复用方式
-
-# 基础 Skills（可独立使用）
-base:
-  - name: requirement-analyzer
-    type: do
-    description: "需求分析执行"
-    path: "knowledge/03-guides/02-analyze-requirement.md"
-
-  - name: design-planner
-    type: do
-    description: "方案设计规划"
-    path: "knowledge/03-guides/03-design-solution.md"
-
-  - name: code-implementer
-    type: do
-    description: "代码实现"
-    path: "knowledge/03-guides/04-implement-code.md"
-
-  - name: test-generator
-    type: do
-    description: "测试生成"
-    path: "knowledge/03-guides/06-generate-tests.md"
-
-# 审查类 Skills（可独立使用）
-review:
-  - name: requirement-reviewer
-    type: review
-    description: "需求审查"
-    path: "knowledge/03-guides/09-review-requirement.md"
-
-  - name: design-reviewer
-    type: review
-    description: "设计审查"
-    path: "knowledge/03-guides/10-review-design.md"
-
-  - name: code-reviewer
-    type: review
-    description: "代码审查"
-    path: "knowledge/03-guides/11-review-code.md"
-
-  - name: security-reviewer
-    type: review
-    description: "安全审查"
-    path: "knowledge/03-guides/13-audit-security.md"
-
-# 分析类 Skills 组合
-analysis:
-  skills:
-    - tech-stack-analyzer
-    - component-discovery
-    - environment-scanner
-  output: "综合分析报告"
-  reuse:
-    - name: tech-stack-analyzer
-      description: "技术栈分析，可单独复用"
-      path: "knowledge/03-guides/26-analyze-tech-stack.md"
-    - name: component-discovery
-      description: "组件发现，可单独复用"
-      path: "knowledge/03-guides/25-discover-component.md"
-    - name: environment-scanner
-      description: "环境扫描，可单独复用"
-      path: "knowledge/03-guides/27-scan-environment.md"
-
-# 评测类 Skills 组合
-evaluation:
-  skills:
-    - ai-effect-evaluator
-    - test-coverage-reviewer
-    - data-validator
-  output: "评测报告"
-  reuse:
-    - name: ai-effect-evaluator
-      description: "AI效果评测"
-      path: "knowledge/03-guides/08-evaluate-ai-effect.md"
-    - name: test-coverage-reviewer
-      description: "测试覆盖率审查"
-      path: "knowledge/03-guides/12-review-testing.md"
-    - name: data-validator
-      description: "数据验证"
-      path: "knowledge/03-guides/39-validate-ai-data.md"
-
-# 支撑类 Skills（可被其他 Skills 引用）
-support:
-  - name: complexity-assessor
-    description: "复杂度评估"
-    path: "knowledge/03-guides/24-assess-complexity.md"
-    reusable: true
-
-  - name: team-orchestrator
-    description: "团队协调器"
-    path: "knowledge/03-guides/01-team-orchestrator.md"
-    reusable: true
-
-  - name: scope-inference
-    description: "范围推断"
-    path: "knowledge/03-guides/23-infer-scope.md"
-    reusable: true
-
-  - name: practice-logger
-    description: "实践记录"
-    path: "knowledge/03-guides/18-log-practice.md"
-    reusable: true
-
-  - name: knowledge-generator
-    description: "知识生成"
-    path: "knowledge/03-guides/29-generate-knowledge.md"
-    reusable: true
-
-  - name: methodology-extractor
-    description: "方法论提取"
-    path: "knowledge/03-guides/22-extract-methodology.md"
-    reusable: true
-
-# Skills 组合模板
-templates:
-  # 环境分析组合
-  environment-analysis:
-    description: "项目环境分析"
-    skills: [environment-scanner, tech-stack-analyzer, component-discovery]
-    output: ".autospec/runtime/environment-report.md"
-
-  # AI评测组合
-  ai-evaluation:
-    description: "AI功能效果评测"
-    skills: [ai-effect-evaluator, test-planner, data-validator]
-    output: ".autospec/specs/{feature}/evaluation-report.md"
-
-  # 安全审计组合
-  security-audit:
-    description: "安全审计"
-    skills: [security-reviewer, code-reviewer]
-    output: ".autospec/specs/{feature}/security-audit.md"
-
-# Skills 引用知识库
-knowledgeReferences:
-  principles: "knowledge/01-principles/"
-  process: "knowledge/02-process/"
-  guides: "knowledge/03-guides/"
-  checklists: "knowledge/04-checklists/"
-  scripts: "scripts/"

package/knowledge/05-config/README.en.md

@@ -1,54 +0,0 @@
-# Config Directory
-
-This directory contains AutoSpec's configuration files, defining validation patterns and team configurations.
-
-## Directory Structure
-
-```
-05-config/
-├── README.md                     # This file
-├── 00-validation-patterns.yaml   # Validation pattern configuration
-├── 02-team-stage.yaml            # Team stage configuration (with triggers)
-├── 03-team-tasks.yaml            # Team tasks configuration
-├── 04-role-composition.yaml      # Role composition configuration (with decision tree)
-├── 05-role-extensions.yaml       # Role extensions configuration
-└── 06-skill-compositions.yaml    # Skill compositions configuration
-```
-
-## Configuration Files
-
-### 00-validation-patterns.yaml
-
-Defines validation patterns for each stage:
-
-```yaml
-# Validation pattern example
-patterns:
-  - name: "build-check"
-    stage: "implementation"
-    commands:
-      - "npm run build"
-    required: true
-```
-
-### 02-team-stage.yaml
-
-Defines team stage configuration with mandatory triggers:
-
-- Stage entry/exit criteria
-- Stage checklists
-- Mandatory triggers (mandatoryTriggers)
-
-### 04-role-composition.yaml
-
-Defines role composition with dynamic decision tree:
-
-- Complexity thresholds
-- Role combinations by stage and complexity
-- Decision tree for dynamic role selection
-- Efficiency optimization
-- Safety brake
-
-## Usage
-
-Configuration files are copied to `.autospec/knowledge/05-config/` during `autospec init` and can be customized per project needs.