@chongyan/autospec 1.0.1 → 1.0.3

package/knowledge/config/team-stage.yaml

@@ -1,95 +0,0 @@
-# 团队阶段配置（AI Native文化融入）
-# 定义不同创业阶段的团队配置、角色组合和文化特质
-
-stages:
-  # 种子期：精简团队 + AI思维
-  seed:
-    description: "初创团队，核心角色覆盖，AI思维融入每个角色"
-    roles:
-      core: [ceo, product-owner, tech-lead]
-      extended: []
-    triggers:
-      simple: [ceo, product-owner]
-      medium: [ceo, product-owner, tech-lead]
-      complex: [ceo, product-owner, tech-lead]
-    culture:
-      - "产品决策考虑AI能力边界"
-      - "技术方案评估AI可行性"
-      - "快速验证AI假设"
-
-  # 成长期：完整团队 + AI/数据角色强化
-  growth:
-    description: "团队扩张，AI工程师成为核心成员"
-    roles:
-      core: [ceo, product-owner, tech-lead, backend-engineer, frontend-engineer, ai-engineer]
-      extended: [quality-engineer, data-engineer]
-    triggers:
-      simple: [ceo, product-owner]
-      medium: [ceo, product-owner, tech-lead, backend-engineer, ai-engineer]
-      complex: [ceo, product-owner, tech-lead, backend-engineer, frontend-engineer, ai-engineer, quality-engineer]
-    culture:
-      - "AI工程师参与核心方案设计"
-      - "数据驱动产品决策"
-      - "AI效果评测体系建立"
-
-  # 成熟期：专业团队 + AI Native运作
-  mature:
-    description: "成熟团队，AI能力全面融入，数据驱动闭环"
-    roles:
-      core: [ceo, product-owner, tech-lead, backend-engineer, frontend-engineer, ai-engineer, data-engineer, quality-engineer]
-      extended: [security-engineer, devops-engineer]
-    triggers:
-      simple: [product-owner, tech-lead]
-      medium: [product-owner, tech-lead, backend-engineer, ai-engineer]
-      complex: [product-owner, tech-lead, backend-engineer, frontend-engineer, ai-engineer, data-engineer, quality-engineer]
-    culture:
-      - "AI能力是产品标配"
-      - "数据驱动决策闭环"
-      - "AI安全与合规体系完善"
-
-# 强制触发规则（所有阶段适用）
-mandatoryTriggers:
-  - condition: "涉及用户数据"
-    roles: [security-engineer]
-    description: "处理用户隐私数据时必须引入安全工程师"
-
-  - condition: "涉及支付/资金交易"
-    roles: [security-engineer]
-    description: "涉及资金交易时必须引入安全工程师"
-
-  - condition: "涉及跨系统变更"
-    roles: [tech-lead, devops-engineer]
-    description: "跨系统变更需要技术负责人和运维工程师参与"
-
-  - condition: "涉及AI/模型"
-    roles: [ai-engineer]
-    description: "AI相关功能必须引入AI工程师"
-
-  - condition: "涉及数据分析/报表"
-    roles: [data-engineer]
-    description: "数据分析功能需要数据工程师参与"
-
-  - condition: "涉及数据管道/ETL"
-    roles: [data-engineer, devops-engineer]
-    description: "数据管道建设需要数据工程师和运维工程师"
-
-  - condition: "涉及AI效果评测"
-    roles: [ai-engineer, quality-engineer]
-    description: "AI效果评测需要AI工程师和质量工程师"
-
-# AI Native 文化原则
-aiNativePrinciples:
-  - name: "AI思维贯穿"
-    description: "每个角色都具备AI思维特质，不只是AI工程师"
-
-  - name: "数据驱动"
-    description: "决策有数据支撑，效果有评测验证"
-
-  - name: "快速验证"
-    description: "AI功能先验证可行性再大规模开发"
-
-  - name: "人机协作"
-    description: "明确AI与人各自擅长的领域"
-
-# 默认阶段
-defaultStage: growth

package/knowledge/config/team-tasks.yaml

@@ -1,139 +0,0 @@
-# 团队任务分配配置
-# 定义各类任务由哪些创业团队组合完成
-
-# 环境衔接任务
-environment-setup:
-  description: "项目环境扫描、技术栈识别、组件发现"
-  team: [tech-lead, devops-engineer, backend-engineer]
-  skills:
-    - environment-scanner
-    - tech-stack-analyzer
-    - component-discovery
-  output: ".autospec/runtime/environment-report.md"
-  triggers:
-    - "autospec init"
-    - "autospec env-sync"
-  aiNative: "AI能力识别，评估项目中AI集成可能性"
-
-# 技术栈分析任务
-tech-analysis:
-  description: "深入分析项目技术栈，给出技术建议"
-  team: [tech-lead, backend-engineer, frontend-engineer, ai-engineer]
-  skills:
-    - tech-stack-analyzer
-    - ai-capability-analyzer
-    - complexity-assessor
-  output: ".autospec/runtime/tech-analysis.md"
-  triggers:
-    - "设计阶段开始前"
-    - "技术选型决策时"
-  aiNative: "评估AI技术选型，分析AI集成复杂度"
-
-# AI效果评测任务
-ai-evaluation:
-  description: "AI模型效果评测，Badcase分析"
-  team: [ai-engineer, quality-engineer, data-engineer]
-  skills:
-    - ai-effect-evaluator
-    - test-planner
-    - data-validator
-  output: ".autospec/specs/{feature}/evaluation-report.md"
-  triggers:
-    - "AI功能开发完成后"
-    - "测试阶段"
-  aiNative: "AI效果评测核心任务，数据驱动验证"
-
-# 安全审计任务
-security-audit:
-  description: "安全漏洞扫描、合规检查"
-  team: [security-engineer, tech-lead, backend-engineer]
-  skills:
-    - security-reviewer
-    - code-reviewer
-  output: ".autospec/specs/{feature}/security-audit.md"
-  triggers:
-    - "涉及用户数据"
-    - "涉及支付/资金交易"
-    - "交付前"
-  aiNative: "AI安全检查：Prompt注入防护、模型安全"
-
-# 一致性检查任务
-consistency-check:
-  description: "跨产物一致性检查"
-  team: [tech-lead, quality-engineer]
-  skills:
-    - consistency-checker
-  output: ".autospec/runtime/consistency-report.md"
-  triggers:
-    - "每个阶段完成后"
-  aiNative: "AI相关假设一致性验证"
-
-# 知识库导入任务
-knowledge-import:
-  description: "导入外部知识库，提取领域知识"
-  team: [tech-lead, ai-engineer, data-engineer]
-  skills:
-    - knowledge-generator
-    - methodology-extractor
-  output: ".autospec/knowledge/imported/"
-  triggers:
-    - "autospec env-import"
-  aiNative: "AI辅助知识提取和结构化"
-
-# 知识库导出任务
-knowledge-export:
-  description: "导出项目知识库"
-  team: [tech-lead, ai-engineer]
-  skills:
-    - knowledge-generator
-  output: "导出到指定位置"
-  triggers:
-    - "autospec env-export"
-  aiNative: "AI辅助知识总结和提炼"
-
-# 组件知识添加任务
-component-add:
-  description: "添加组件知识"
-  team: [tech-lead, backend-engineer]
-  skills:
-    - component-discovery
-  output: ".autospec/knowledge/environment/component-knowledge.md"
-  triggers:
-    - "autospec component-add"
-  aiNative: "识别组件AI能力"
-
-# 阶段门禁评估任务
-stage-gate:
-  description: "阶段产出物评估"
-  team: [tech-lead, quality-engineer]
-  skills:
-    - stage-gate-evaluator
-  output: ".autospec/runtime/stage-gate-report.md"
-  triggers:
-    - "每个阶段完成时"
-  aiNative: "AI功能完成度评估"
-
-# 失败诊断任务
-failure-diagnosis:
-  description: "失败原因诊断"
-  team: [tech-lead, quality-engineer, ai-engineer]
-  skills:
-    - failure-diagnostician
-  output: ".autospec/runtime/failure-diagnosis.md"
-  triggers:
-    - "验证失败3次后"
-  aiNative: "AI辅助失败原因分析"
-
-# 任务执行模式
-executionModes:
-  parallel:
-    description: "并行执行，信息隔离"
-    useCase: "审查类任务"
-
-  sequential:
-    description: "串行执行，依赖传递"
-    useCase: "有依赖关系的任务"
-
-  collaborative:
-    description: "协作执行，共同讨论"
-    useCase: "需要达成共识的任务"

package/knowledge/config/team-triggers.yaml

@@ -1,198 +0,0 @@
-# 团队角色触发配置
-# 定义复杂度阈值、强制触发规则、阶段-角色映射
-
-# ============================================
-# 复杂度阈值
-# ============================================
-complexity_threshold:
-  simple: 5      # <=5 简单任务，快速通道
-  medium: 8      # 6-8 中等任务，引入核心角色
-  complex: 9     # >=9 复杂任务，引入完整团队
-
-# ============================================
-# 强制触发规则（不受复杂度影响）
-# ============================================
-force_triggers:
-  # 安全相关
-  - id: user_data
-    condition: "涉及用户数据存储或处理"
-    keywords: ["用户数据", "个人信息", "用户信息", "隐私数据", "用户资料"]
-    roles: ["security-engineer"]
-
-  - id: payment
-    condition: "涉及支付或资金交易功能"
-    keywords: ["支付", "付款", "充值", "提现", "转账", "资金交易", "订单支付"]
-    roles: ["security-engineer"]
-
-  - id: external_api
-    condition: "涉及外部API调用"
-    keywords: ["外部API", "第三方接口", "开放平台", "外部服务", "回调接口"]
-    roles: ["security-engineer"]
-
-  # 架构相关
-  - id: new_architecture
-    condition: "涉及新架构或框架引入"
-    keywords: ["新架构", "架构调整", "架构重构", "新框架", "技术栈升级", "框架迁移"]
-    roles: ["tech-lead"]
-
-  - id: cross_system
-    condition: "涉及跨系统变更"
-    keywords: ["跨系统", "多系统", "系统集成", "系统对接", "微服务"]
-    roles: ["tech-lead", "devops-engineer"]
-
-  # 部署相关
-  - id: new_service
-    condition: "涉及新服务部署"
-    keywords: ["新服务", "服务部署", "新模块部署", "独立服务"]
-    roles: ["devops-engineer"]
-
-  - id: db_change
-    condition: "涉及数据库变更"
-    keywords: ["数据库变更", "表结构", "数据迁移", "数据库升级"]
-    roles: ["devops-engineer"]
-
-  - id: infrastructure
-    condition: "涉及基础设施变更"
-    keywords: ["基础设施", "服务器", "容器", "K8s", "云资源", "网络配置"]
-    roles: ["devops-engineer"]
-
-# ============================================
-# 阶段-角色映射
-# ============================================
-stage_role_mapping:
-
-  # 需求阶段
-  requirement:
-    simple:
-      - ceo
-      - product-owner
-    medium:
-      - ceo
-      - product-owner
-      - tech-lead
-    complex:
-      - ceo
-      - product-owner
-      - tech-lead
-      - backend-engineer
-      - frontend-engineer
-      - quality-engineer
-    # 条件触发
-    conditional:
-      - roles: ["security-engineer"]
-        condition: "dataSensitivity >= 2"
-      - roles: ["ai-engineer"]
-        condition: "hasAISubsystem"
-      - roles: ["data-engineer"]
-        condition: "hasDataSubsystem"
-
-  # 设计阶段
-  design:
-    simple:
-      - tech-lead
-    medium:
-      - tech-lead
-      - backend-engineer
-      - frontend-engineer
-    complex:
-      - tech-lead
-      - backend-engineer
-      - frontend-engineer
-      - data-engineer
-      - ai-engineer
-      - quality-engineer
-    conditional:
-      - roles: ["security-engineer"]
-        condition: "dataSensitivity >= 2"
-      - roles: ["devops-engineer"]
-        condition: "deploymentRisk >= 2"
-      - roles: ["devops-engineer"]
-        condition: "hasArchitectureChange"
-
-  # 编码阶段
-  code:
-    simple:
-      - tech-lead
-    medium:
-      - tech-lead
-      - relevant-engineer
-    complex:
-      - tech-lead
-      - backend-engineer
-      - frontend-engineer
-      - data-engineer
-      - ai-engineer
-    conditional:
-      - roles: ["security-engineer"]
-        condition: "dataSensitivity >= 3"
-
-  # 测试阶段
-  test:
-    simple:
-      - quality-engineer
-    medium:
-      - quality-engineer
-      - tech-lead
-    complex:
-      - quality-engineer
-      - tech-lead
-      - backend-engineer
-      - frontend-engineer
-    conditional:
-      - roles: ["security-engineer"]
-        condition: "dataSensitivity >= 3"
-
-  # 交付阶段
-  delivery:
-    simple:
-      - quality-engineer
-      - tech-lead
-    medium:
-      - quality-engineer
-      - tech-lead
-    complex:
-      - quality-engineer
-      - tech-lead
-      - devops-engineer
-    conditional:
-      - roles: ["security-engineer"]
-        condition: "dataSensitivity >= 2"
-      - roles: ["devops-engineer"]
-        condition: "hasDeploymentRisk"
-
-# ============================================
-# 子系统类型-工程师映射
-# ============================================
-subsystem_engineer_mapping:
-  backend: backend-engineer
-  frontend: frontend-engineer
-  web: frontend-engineer
-  mobile: frontend-engineer
-  data: data-engineer
-  ai: ai-engineer
-  ml: ai-engineer
-  model: ai-engineer
-
-# ============================================
-# 复杂度维度权重（用于微调）
-# ============================================
-dimension_weights:
-  requirement: 1.0   # 需求复杂度
-  technical: 1.0     # 技术复杂度
-  data_sensitivity: 1.0  # 数据敏感度
-  business: 1.0      # 业务复杂度
-
-# ============================================
-# 快速通道规则
-# ============================================
-fast_track:
-  enabled: true
-  max_score: 5
-  # 快速通道跳过的检查
-  skip_checks:
-    - expert_review  # 跳过专家审查
-    - full_team_review  # 跳过完整团队审查
-  # 快速通道仍需执行的检查
-  required_checks:
-    - layer1_validation
-    - basic_review

package/knowledge/config/validation-patterns.yaml

@@ -1,137 +0,0 @@
-# AutoSpec 验证命令模式配置
-# 用于 Layer 1 验证的命令检测
-
-# ============================================================
-# Layer 1 验证命令模式
-# ============================================================
-validationCommands:
-  test:
-    pattern: "\\b(npm test|npm run test|jest|mocha|pytest|go test|cargo test|vitest|ava|tap|bun test)\\b"
-    description: 测试命令
-
-  build:
-    pattern: "\\b(npm run build|cargo build|go build|make|gradle|mvn|tsc|bun build)\\b"
-    description: 构建命令
-
-  lint:
-    pattern: "\\b(eslint|tslint|standard|xo|biome|eslint-cli)\\b"
-    description: Lint 检查命令
-
-  typecheck:
-    pattern: "\\b(npx tsc|tsc --noEmit|flow|mypy|pyright|pyre)\\b"
-    description: 类型检查命令
-
-  format:
-    pattern: "\\b(prettier|black|gofmt|rustfmt|clang-format)\\b"
-    description: 格式化命令
-
-  security:
-    pattern: "\\b(npm audit|yarn audit|snyk|safety|pip-audit|trivy)\\b"
-    description: 安全检查命令
-
-# ============================================================
-# 冻结区文件模式
-# ============================================================
-frozenPatterns:
-  - pattern: "constitution\\.md$"
-    description: 宪法文件
-
-  - pattern: "evolution\\.md$"
-    description: 进化机制文件
-
-  - pattern: "design-philosophy\\.md$"
-    description: 设计哲学文件
-
-  - pattern: "pipeline/overview\\.md$"
-    description: 流程概览文件
-
-# ============================================================
-# 开发文件模式
-# ============================================================
-developmentPatterns:
-  - pattern: "\\.(js|ts|jsx|tsx|py|java|go|rs|cpp|c|h|php|rb|swift|kt|scala|vue|svelte)\\b"
-    description: 源代码文件
-
-  - pattern: "package\\.json$"
-    description: NPM 配置
-
-  - pattern: "pom\\.xml$"
-    description: Maven 配置
-
-  - pattern: "build\\.gradle"
-    description: Gradle 配置
-
-  - pattern: "Cargo\\.toml$"
-    description: Cargo 配置
-
-  - pattern: "go\\.mod$"
-    description: Go 模块配置
-
-  - pattern: "pyproject\\.toml$"
-    description: Python 项目配置
-
-# ============================================================
-# 配置文件模式
-# ============================================================
-configFilePatterns:
-  - pattern: "package\\.json$"
-    description: NPM 配置
-
-  - pattern: "tsconfig.*\\.json$"
-    description: TypeScript 配置
-
-  - pattern: "\\.eslintrc"
-    description: ESLint 配置
-
-  - pattern: "(webpack|vite|rollup).*config"
-    description: 打包工具配置
-
-  - pattern: "docker"
-    description: Docker 相关
-
-  - pattern: "\\.env"
-    description: 环境变量文件
-
-# ============================================================
-# 敏感信息检测模式
-# ============================================================
-sensitivePatterns:
-  - pattern: "password\\s*[:=]\\s*['\"][^'\"]+['\"]"
-    description: 密码
-
-  - pattern: "secret\\s*[:=]\\s*['\"][^'\"]+['\"]"
-    description: 密钥
-
-  - pattern: "api[_-]?key\\s*[:=]\\s*['\"][^'\"]+['\"]"
-    description: API Key
-
-  - pattern: "token\\s*[:=]\\s*['\"][^'\"]+['\"]"
-    description: Token
-
-  - pattern: "private[_-]?key\\s*[:=]\\s*['\"][^'\"]+['\"]"
-    description: 私钥
-
-# ============================================================
-# 危险命令模式
-# ============================================================
-dangerousPatterns:
-  - pattern: "rm\\s+-rf"
-    description: 强制删除
-
-  - pattern: "sudo\\s+"
-    description: 提权命令
-
-  - pattern: "mkfs"
-    description: 格式化磁盘
-
-  - pattern: "dd\\s+if="
-    description: 磁盘操作
-
-  - pattern: ">\\s*/dev/"
-    description: 设备写入
-
-  - pattern: "curl.*\\|.*sh"
-    description: 远程脚本执行
-
-  - pattern: "wget.*\\|.*sh"
-    description: 远程脚本执行

package/knowledge/domain/README.md

@@ -1,115 +0,0 @@
-# 业务知识沉淀体系
-
-> 定位：将项目特有的业务知识结构化沉淀，作为上下文注入各阶段。
-
-## 目录结构
-
-```
-knowledge/domain/
-├── README.md      # 本文件：使用指南
-├── glossary.md    # 术语表：统一业务概念定义
-├── rules.md       # 业务规则：规则ID化，便于追溯
-└── flows/         # 业务流程图：Mermaid格式，可视化业务逻辑
-    └── README.md  # 流程图规范
-```
-
-## 使用方式
-
-### 阶段注入
-
-| 阶段 | 注入内容 | 用途 |
-|------|---------|------|
-| 需求分析 | glossary + rules | 理解业务背景，避免歧义 |
-| 方案设计 | glossary + flows | 设计符合业务逻辑的技术方案 |
-| 代码审查 | rules | 检验代码是否遵循业务规则 |
-| 测试验证 | rules + flows | 构造测试场景，覆盖业务流程 |
-
-### 与环境知识的关系
-
-| 知识类型 | 处理层面 | 示例 |
-|---------|---------|------|
-| **环境知识** | 技术层 | 中间件配置、组件库、CI/CD |
-| **业务知识** | 业务层 | 术语定义、业务规则、流程图 |
-
-两者互补，共同构成立体上下文。
-
-### 与项目产出物的关系
-
-业务知识是**项目无关的通用知识**，产出物中的业务规则应引用此处定义：
-
-```
-产出物 requirement.md 中的业务规则
-    ↓ 引用
-knowledge/domain/rules.md 中的 BR-ID
-```
-
-## 进化分区
-
-| 内容 | 进化分区 | 变更方式 |
-|------|---------|---------|
-| glossary.md | 自由区 | 从需求文档自动提取 + 人工确认 |
-| rules.md | 受控区 | 从 practice-log 提取 + 人工审批 |
-| flows/ | 自由区 | 从设计文档提取 + validator 验证 |
-
-## 脱敏原则
-
-业务知识沉淀遵循以下脱敏原则：
-
-- ❌ 不记录具体客户信息
-- ❌ 不记录敏感金额数据
-- ❌ 不使用公司/产品特有名称
-- ✅ 使用通用化示例：用"支付"替代特指渠道
-- ✅ 使用占位符：`user_001`、`order_123`
-
-## 快速开始
-
-### 1. 初始化术语表
-
-```bash
-# 从需求文档提取候选术语
-# 高频词、首字母缩写、专用名词
-```
-
-### 2. 定义业务规则
-
-```markdown
-# 在 rules.md 中添加
-| 规则ID | 规则名称 | 规则描述 | 适用场景 | 校验方式 |
-|--------|---------|---------|---------|---------|
-| BR-01 | （规则名） | （描述） | （场景） | （方式） |
-```
-
-### 3. 绘制业务流程
-
-```markdown
-# 在 flows/ 中创建
-# 使用 Mermaid flowchart 格式
-```
-
-## 维护指南
-
-### 术语冲突处理
-
-当术语定义冲突时：
-1. 以 `glossary.md` 为准
-2. 如有歧义，在需求分析阶段澄清
-3. 澄清后更新 `glossary.md`
-
-### 规则变更流程
-
-1. 识别规则变更需求（来自需求/缺陷/反馈）
-2. 在 `rules.md` 中更新规则
-3. 标注变更版本和原因
-4. 通知相关阶段（设计/测试/审查）
-
-### 流程图更新
-
-1. 业务流程变更时同步更新
-2. 保持与设计文档的一致性
-3. 版本化记录变更历史
-
----
-
-**维护者**: 项目团队
-**进化分区**: 自由区/受控区
-**关联文档**: `knowledge/environment/README.md`