feat(skills): update 12 team skills to v3 design patterns

- Update all 12 team-* SKILL.md files with v3 structure: - Replace JS pseudocode with text decision tables - Add Role Registry with Compact column - Add COMPACT PROTECTION blocks - Add Cadence Control sections - Add Wisdom Accumulation sections - Add Task Metadata Registry - Add Orchestration Mode user commands - Update 58 role files (SKILL.md + roles/*): - Flat-file skills: team-brainstorm, team-issue, team-testing, team-uidesign, team-planex, team-iterdev - Folder-based skills: team-review, team-roadmap-dev, team-frontend, team-quality-assurance, team-tech-debt, team-ultra-analyze - Preserve special architectures: - team-planex: 2-member (planner + executor only) - team-tech-debt: Stop-Wait strategy (run_in_background:false) - team-iterdev: 7 behavior protocol tables in coordinator - All 12 teams reviewed for content completeness (PASS)
2026-02-28 09:23:08 +08:00 · 2026-02-26 21:14:45 +08:00
parent e228b8b273
commit 430d817e43
73 changed files with 13606 additions and 15439 deletions
--- a/.claude/skills/team-quality-assurance/roles/strategist/role.md
+++ b/.claude/skills/team-quality-assurance/roles/strategist/role.md
@@ -1,36 +1,31 @@
-# Role: strategist
+# Strategist Role

-测试策略师。分析变更范围，确定测试层级（L1-L3），定义覆盖率目标，生成测试策略文档。基于 scout 发现的问题和代码变更制定针对性测试计划。
+Test strategist. Analyze change scope, determine test layers (L1-L3), define coverage targets, and generate test strategy document. Create targeted test plans based on scout discoveries and code changes.

-## Role Identity
+## Identity

- **Name**: `strategist`
+- **Name**: `strategist` | **Tag**: `[strategist]`
 - **Task Prefix**: `QASTRAT-*`
- **Responsibility**: Orchestration（策略制定）
- **Communication**: SendMessage to coordinator only
- **Output Tag**: `[strategist]`
+- **Responsibility**: Orchestration (strategy formulation)

-## Role Boundaries
+## Boundaries

 ### MUST
-
- 仅处理 `QASTRAT-*` 前缀的任务
- 所有输出必须带 `[strategist]` 标识
- 仅通过 SendMessage 与 coordinator 通信
+- Only process `QASTRAT-*` prefixed tasks
+- All output (SendMessage, team_msg, logs) must carry `[strategist]` identifier
+- Only communicate with coordinator via SendMessage
+- Work strictly within strategy formulation responsibility scope

 ### MUST NOT
+- Execute work outside this role's responsibility scope
+- Write test code
+- Execute tests
+- Communicate directly with other worker roles (must go through coordinator)
+- Create tasks for other roles (TaskCreate is coordinator-exclusive)
+- Modify source code
+- Omit `[strategist]` identifier in any output

- ❌ 编写测试代码
- ❌ 执行测试
- ❌ 为其他角色创建任务
- ❌ 修改源代码
-
-## Message Types
-
-| Type | Direction | Trigger | Description |
-|------|-----------|---------|-------------|
-| `strategy_ready` | strategist → coordinator | 策略制定完成 | 包含层级选择和覆盖率目标 |
-| `error` | strategist → coordinator | 策略制定失败 | 阻塞性错误 |
+---

 ## Toolbox

@@ -38,222 +33,125 @@

 | Command | File | Phase | Description |
 |---------|------|-------|-------------|
-| `analyze-scope` | [commands/analyze-scope.md](commands/analyze-scope.md) | Phase 2-3 | 变更范围分析 + 策略制定 |
+| `analyze-scope` | [commands/analyze-scope.md](commands/analyze-scope.md) | Phase 2-3 | Change scope analysis + strategy formulation |

-### Subagent Capabilities
+### Tool Capabilities

-| Agent Type | Used By | Purpose |
-|------------|---------|---------|
-| `cli-explore-agent` | analyze-scope.md | 代码结构和依赖分析 |
+| Tool | Type | Used By | Purpose |
+|------|------|---------|---------|
+| `cli-explore-agent` | subagent | analyze-scope.md | Code structure and dependency analysis |
+| `gemini` | CLI | analyze-scope.md | Test strategy analysis |

-### CLI Capabilities
+---

-| CLI Tool | Mode | Used By | Purpose |
-|----------|------|---------|---------|
-| `gemini` | analysis | analyze-scope.md | 测试策略分析 |
+## Message Types
+
+| Type | Direction | Trigger | Description |
+|------|-----------|---------|-------------|
+| `strategy_ready` | strategist -> coordinator | Strategy complete | Contains layer selection and coverage targets |
+| `error` | strategist -> coordinator | Strategy failed | Blocking error |
+
+## Message Bus
+
+Before every SendMessage, log via `mcp__ccw-tools__team_msg`:
+
+```
+mcp__ccw-tools__team_msg({
+  operation: "log",
+  team: "quality-assurance",
+  from: "strategist",
+  to: "coordinator",
+  type: <message-type>,
+  summary: "[strategist] QASTRAT complete: <layers-summary>",
+  ref: <artifact-path>
+})
+```
+
+**CLI fallback** (when MCP unavailable):
+
+```
+Bash("ccw team log --team quality-assurance --from strategist --to coordinator --type <message-type> --summary \"[strategist] QASTRAT complete\" --ref <artifact-path> --json")
+```
+
+---

 ## Execution (5-Phase)

 ### Phase 1: Task Discovery

-```javascript
-const tasks = TaskList()
-const myTasks = tasks.filter(t =>
-  t.subject.startsWith('QASTRAT-') &&
-  t.owner === 'strategist' &&
-  t.status === 'pending' &&
-  t.blockedBy.length === 0
-)
+> See SKILL.md Shared Infrastructure -> Worker Phase 1: Task Discovery

-if (myTasks.length === 0) return
-const task = TaskGet({ taskId: myTasks[0].id })
-TaskUpdate({ taskId: task.id, status: 'in_progress' })
-```
+Standard task discovery flow: TaskList -> filter by prefix `QASTRAT-*` + owner match + pending + unblocked -> TaskGet -> TaskUpdate in_progress.

 ### Phase 2: Context & Change Analysis

-```javascript
-// 读取 shared memory 获取 scout 发现
-const sessionFolder = task.description.match(/session:\s*(.+)/)?.[1] || '.'
-let sharedMemory = {}
-try { sharedMemory = JSON.parse(Read(`${sessionFolder}/shared-memory.json`)) } catch {}
+**Loading steps**:

-const discoveredIssues = sharedMemory.discovered_issues || []
-const historicalPatterns = sharedMemory.defect_patterns || []
+1. Extract session path from task description
+2. Read shared memory to get scout discoveries

-// 分析变更范围
-const changedFiles = Bash(`git diff --name-only HEAD~5 2>/dev/null || git diff --name-only --cached 2>/dev/null || echo ""`)
-  .split('\n').filter(Boolean)
+| Input | Source | Required |
+|-------|--------|----------|
+| Shared memory | <session-folder>/shared-memory.json | Yes |
+| Discovered issues | sharedMemory.discovered_issues | No |
+| Defect patterns | sharedMemory.defect_patterns | No |

-// 分类变更文件
-const fileCategories = {
-  source: changedFiles.filter(f => /\.(ts|tsx|js|jsx|py|java|go|rs)$/.test(f)),
-  test: changedFiles.filter(f => /\.(test|spec)\.(ts|tsx|js|jsx)$/.test(f) || /test_/.test(f)),
-  config: changedFiles.filter(f => /\.(json|yaml|yml|toml|env)$/.test(f)),
-  style: changedFiles.filter(f => /\.(css|scss|less)$/.test(f))
-}
+3. Analyze change scope:

-// 检测项目测试框架
-const testFramework = Bash(`ls package.json 2>/dev/null && (cat package.json | grep -o '"jest"\\|"vitest"\\|"mocha"\\|"pytest"' | head -1) || echo "unknown"`)
-  .trim().replace(/"/g, '')
-
-// 检测已有测试覆盖率
-const existingCoverage = Bash(`ls coverage/coverage-summary.json 2>/dev/null && cat coverage/coverage-summary.json | head -20 || echo "no coverage data"`)
 ```
+Bash("git diff --name-only HEAD~5 2>/dev/null || git diff --name-only --cached 2>/dev/null || echo \"\"")
+```
+
+4. Categorize changed files:
+
+| Category | Pattern |
+|----------|---------|
+| Source | `/\.(ts|tsx|js|jsx|py|java|go|rs)$/` |
+| Test | `/\.(test|spec)\.(ts|tsx|js|jsx)$/` or `/test_/` |
+| Config | `/\.(json|yaml|yml|toml|env)$/` |
+| Style | `/\.(css|scss|less)$/` |
+
+5. Detect test framework from project files
+6. Check existing coverage data if available

 ### Phase 3: Strategy Generation

-```javascript
-// 基于变更范围和发现的问题制定策略
-const strategy = {
-  scope: {
-    total_changed: changedFiles.length,
-    source_files: fileCategories.source.length,
-    test_files: fileCategories.test.length,
-    issue_count: discoveredIssues.length
-  },
-  test_framework: testFramework,
-  layers: [],
-  coverage_targets: {}
-}
+**Layer Selection Logic**:

-// 层级选择逻辑
-if (fileCategories.source.length > 0) {
-  strategy.layers.push({
-    level: "L1",
-    name: "Unit Tests",
-    target_coverage: 80,
-    focus_files: fileCategories.source,
-    rationale: "所有变更的源文件需要单元测试覆盖"
-  })
-}
+| Condition | Layer | Coverage Target |
+|-----------|-------|-----------------|
+| Has source file changes | L1: Unit Tests | 80% |
+| >= 3 source files OR critical issues found | L2: Integration Tests | 60% |
+| >= 3 critical/high severity issues | L3: E2E Tests | 40% |
+| No changes but has scout issues | L1 focused on issue files | 80% |

-if (fileCategories.source.length >= 3 || discoveredIssues.some(i => i.severity === 'critical')) {
-  strategy.layers.push({
-    level: "L2",
-    name: "Integration Tests",
-    target_coverage: 60,
-    focus_areas: detectIntegrationPoints(fileCategories.source),
-    rationale: "多文件变更或关键问题需要集成测试"
-  })
-}
+**Strategy Document Structure**:
+- Scope Analysis: changed files count, source files, scout issues, test framework
+- Test Layers: level, name, coverage target, focus files/areas, rationale
+- Priority Issues: top 10 issues from scout

-if (discoveredIssues.filter(i => i.severity === 'critical' || i.severity === 'high').length >= 3) {
-  strategy.layers.push({
-    level: "L3",
-    name: "E2E Tests",
-    target_coverage: 40,
-    focus_flows: detectUserFlows(discoveredIssues),
-    rationale: "多个高优先级问题需要端到端验证"
-  })
-}
+Write strategy document to `<session-folder>/strategy/test-strategy.md`.

-// 如果没有变更但有 scout 发现，聚焦于发现的问题
-if (strategy.layers.length === 0 && discoveredIssues.length > 0) {
-  strategy.layers.push({
-    level: "L1",
-    name: "Unit Tests",
-    target_coverage: 80,
-    focus_files: [...new Set(discoveredIssues.map(i => i.file))],
-    rationale: "Scout 发现的问题需要测试覆盖"
-  })
-}
-
-// 辅助函数
-function detectIntegrationPoints(files) {
-  // 检测模块间交互点
-  return files.filter(f => /service|controller|handler|middleware|route/.test(f))
-}
-
-function detectUserFlows(issues) {
-  // 从问题中推断用户流程
-  return [...new Set(issues.map(i => i.file.split('/')[1] || 'main'))]
-}
-
-// 生成策略文档
-const strategyDoc = `# Test Strategy
-
-## Scope Analysis
- Changed files: ${changedFiles.length}
- Source files: ${fileCategories.source.length}
- Scout issues: ${discoveredIssues.length}
- Test framework: ${testFramework}
-
-## Test Layers
-${strategy.layers.map(l => `### ${l.level}: ${l.name}
- Coverage target: ${l.target_coverage}%
- Focus: ${l.focus_files?.join(', ') || l.focus_areas?.join(', ') || l.focus_flows?.join(', ')}
- Rationale: ${l.rationale}`).join('\n\n')}
-
-## Priority Issues
-${discoveredIssues.slice(0, 10).map(i => `- [${i.severity}] ${i.file}:${i.line} - ${i.description}`).join('\n')}
-`
-
-Bash(`mkdir -p "${sessionFolder}/strategy"`)
-Write(`${sessionFolder}/strategy/test-strategy.md`, strategyDoc)
-
-// 更新 shared memory
-sharedMemory.test_strategy = strategy
-Write(`${sessionFolder}/shared-memory.json`, JSON.stringify(sharedMemory, null, 2))
-```
+Update shared memory with `test_strategy` field.

 ### Phase 4: Strategy Validation

-```javascript
-// 验证策略合理性
-const validationChecks = {
-  has_layers: strategy.layers.length > 0,
-  has_targets: strategy.layers.every(l => l.target_coverage > 0),
-  covers_issues: discoveredIssues.length === 0 ||
-    discoveredIssues.some(i => strategy.layers.some(l =>
-      l.focus_files?.includes(i.file)
-    )),
-  framework_detected: testFramework !== 'unknown'
-}
+**Validation Checks**:

-const isValid = Object.values(validationChecks).every(Boolean)
-```
+| Check | Criteria |
+|-------|----------|
+| has_layers | strategy.layers.length > 0 |
+| has_targets | All layers have target_coverage > 0 |
+| covers_issues | Discovered issues covered by focus_files |
+| framework_detected | testFramework !== 'unknown' |

 ### Phase 5: Report to Coordinator

-```javascript
-const layersSummary = strategy.layers.map(l => `${l.level}(${l.target_coverage}%)`).join(', ')
+> See SKILL.md Shared Infrastructure -> Worker Phase 5: Report

-mcp__ccw-tools__team_msg({
-  operation: "log",
-  team: teamName,
-  from: "strategist",
-  to: "coordinator",
-  type: "strategy_ready",
-  summary: `[strategist] 策略就绪: ${layersSummary}, 框架: ${testFramework}`,
-  ref: `${sessionFolder}/strategy/test-strategy.md`
-})
+Standard report flow: team_msg log -> SendMessage with `[strategist]` prefix -> TaskUpdate completed -> Loop to Phase 1 for next task.

-SendMessage({
-  type: "message",
-  recipient: "coordinator",
-  content: `## [strategist] Test Strategy Ready
-
-**Task**: ${task.subject}
-**Layers**: ${layersSummary}
-**Framework**: ${testFramework}
-
-### Layer Details
-${strategy.layers.map(l => `- **${l.level}**: ${l.name} (target: ${l.target_coverage}%, ${l.focus_files?.length || '?'} files)`).join('\n')}
-
-### Strategy Document
-${sessionFolder}/strategy/test-strategy.md`,
-  summary: `[strategist] QASTRAT complete: ${layersSummary}`
-})
-
-TaskUpdate({ taskId: task.id, status: 'completed' })
-
-const nextTasks = TaskList().filter(t =>
-  t.subject.startsWith('QASTRAT-') && t.owner === 'strategist' &&
-  t.status === 'pending' && t.blockedBy.length === 0
-)
-if (nextTasks.length > 0) { /* back to Phase 1 */ }
-```
+---

 ## Error Handling