maestro-flow 0.4.9 → 0.4.10

package/.agy/skills/team-tech-debt/roles/scanner/role.md

@@ -0,0 +1,90 @@
+---
+role: scanner
+prefix: TDSCAN
+inner_loop: false
+message_types: [state_update]
+---
+
+# Tech Debt Scanner
+
+Multi-dimension tech debt scanner. Scan codebase across 5 dimensions (code, architecture, testing, dependency, documentation), produce structured debt inventory with severity rankings.
+
+## Phase 2: Context & Environment Detection
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Scan scope | task description (regex: `scope:\s*(.+)`) | No (default: `**/*`) |
+| Session path | task description (regex: `session:\s*(.+)`) | Yes |
+| .msg/meta.json | <session>/.msg/meta.json | Yes |
+
+1. Extract session path and scan scope from task description
+2. Load debug specs: Run `ccw spec load --category debug` for known issues, workarounds, and root-cause notes
+3. Read .msg/meta.json for team context
+3. Detect project type and framework:
+
+| Signal File | Project Type |
+|-------------|-------------|
+| package.json + React/Vue/Angular | Frontend Node |
+| package.json + Express/Fastify/NestJS | Backend Node |
+| pyproject.toml / requirements.txt | Python |
+| go.mod | Go |
+| No detection | Generic |
+
+4. Determine scan dimensions (default: code, architecture, testing, dependency, documentation)
+5. Detect perspectives from task description:
+
+| Condition | Perspective |
+|-----------|-------------|
+| `security\|auth\|inject\|xss` | security |
+| `performance\|speed\|optimize` | performance |
+| `quality\|clean\|maintain\|debt` | code-quality |
+| `architect\|pattern\|structure` | architecture |
+| Default | code-quality + architecture |
+
+6. Assess complexity:
+
+| Score | Complexity | Strategy |
+|-------|------------|----------|
+| >= 4 | High | Triple Fan-out: CLI explore + CLI 5 dimensions + multi-perspective Gemini |
+| 2-3 | Medium | Dual Fan-out: CLI explore + CLI 3 dimensions |
+| 0-1 | Low | Inline: ACE search + Grep |
+
+## Phase 3: Multi-Dimension Scan
+
+**Low Complexity** (inline):
+- Use `mcp__ace-tool__search_context` for code smells, TODO/FIXME, deprecated APIs, complex functions, dead code, missing tests
+- Classify findings into dimensions
+
+**Medium/High Complexity** (Fan-out):
+- Fan-out A: CLI exploration (structure, patterns, dependencies angles) via `maestro delegate --role explore --mode analysis`
+- Fan-out B: CLI dimension analysis (parallel per dimension -- code, architecture, testing, dependency, documentation) via `--role analyze`
+- Fan-out C (High only): Multi-perspective analysis (security, performance, code-quality, architecture) via `--role analyze`
+- Fan-in: Merge results, cross-deduplicate by file:line, boost severity for multi-source findings
+
+**Standardize each finding**:
+
+| Field | Description |
+|-------|-------------|
+| `id` | `TD-NNN` (sequential) |
+| `dimension` | code, architecture, testing, dependency, documentation |
+| `severity` | critical, high, medium, low |
+| `file` | File path |
+| `line` | Line number |
+| `description` | Issue description |
+| `suggestion` | Fix suggestion |
+| `estimated_effort` | small, medium, large, unknown |
+
+### Tech Profile Scan
+
+After multi-dimension scan, emit context-aware trigger signals (based on detected codebase characteristics):
+
+1. Check debt dimensions → signals (`legacy_patterns`, `test_gap`, `perf_sensitive`)
+2. Check detected patterns → risk signals (`sql_detected`, `auth_detected`, `scaling_concern`, `injection_risk`)
+3. Include `tech_profile` in Phase 5 state_update data
+
+## Phase 4: Aggregate & Save
+
+1. Deduplicate findings across Fan-out layers (file:line key), merge cross-references
+2. Sort by severity (cross-referenced items boosted)
+3. Write `<session>/scan/debt-inventory.json` with scan_date, dimensions, total_items, by_dimension, by_severity, items
+4. Update .msg/meta.json with `debt_inventory` array and `debt_score_before` count

package/.agy/skills/team-tech-debt/roles/validator/role.md

@@ -0,0 +1,78 @@
+---
+role: validator
+prefix: TDVAL
+inner_loop: false
+message_types: [state_update]
+---
+
+# Tech Debt Validator
+
+Cleanup result validator. Run test suite, type checks, lint checks, and quality analysis to verify debt cleanup introduced no regressions. Compare before/after debt scores, produce validation-report.json.
+
+## Phase 2: Load Context
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Session path | task description (regex: `session:\s*(.+)`) | Yes |
+| .msg/meta.json | <session>/.msg/meta.json | Yes |
+| Fix log | <session>/fixes/fix-log.json | No |
+
+1. Extract session path from task description
+2. Read .msg/meta.json for: worktree.path, debt_inventory, fix_results, debt_score_before
+3. Determine command prefix: `cd "<worktree-path>" && ` if worktree exists
+4. Read fix-log.json for modified files list
+5. Detect available validation tools in worktree:
+
+| Signal | Tool | Method |
+|--------|------|--------|
+| package.json + npm | npm test | Test suite |
+| pytest available | python -m pytest | Test suite |
+| npx tsc available | npx tsc --noEmit | Type check |
+| npx eslint available | npx eslint | Lint check |
+
+## Phase 3: Run Validation Checks
+
+Execute 4-layer validation (all commands in worktree):
+
+**1. Test Suite**:
+- Run `npm test` or `python -m pytest` in worktree
+- PASS if no FAIL/error/failed keywords; FAIL with regression count otherwise
+- Skip with "no-tests" if no test runner available
+
+**2. Type Check**:
+- Run `npx tsc --noEmit` in worktree
+- Count `error TS` occurrences for error count
+
+**3. Lint Check**:
+- Run `npx eslint --no-error-on-unmatched-pattern <modified-files>` in worktree
+- Count error occurrences
+
+**4. Quality Analysis** (optional, when > 5 modified files):
+- Use gemini CLI to compare code quality before/after
+- Assess complexity, duplication, naming quality improvements
+
+**Debt Score Calculation**:
+- debt_score_after = debt items NOT in modified files (remaining unfixed items)
+- improvement_percentage = ((before - after) / before) * 100
+
+**Auto-fix attempt** (when total_regressions <= 3):
+- Use CLI tool to fix regressions in worktree:
+  ```
+  run_command({
+    command: `cd "${worktreePath}" && maestro delegate "PURPOSE: Fix regressions found in validation
+  TASK: ${regressionDetails}
+  MODE: write
+  CONTEXT: @${modifiedFiles.join(' @')}
+  EXPECTED: Fixed regressions
+  CONSTRAINTS: Fix only regressions | Preserve debt cleanup changes | No suppressions" --tool gemini --mode write`,
+    run_in_background: false
+  })
+  ```
+- Re-run validation checks after fix attempt
+
+## Phase 4: Compare & Report
+
+1. Calculate: total_regressions = test_regressions + type_errors + lint_errors; passed = (total_regressions === 0)
+2. Write `<session>/validation/validation-report.json` with: validation_date, passed, regressions, checks (per-check status), debt_score_before, debt_score_after, improvement_percentage
+3. Update .msg/meta.json with `validation_results` and `debt_score_after`
+4. Select message type: `validation_complete` if passed, `regression_found` if not

package/.agy/skills/team-tech-debt/specs/pipelines.md

@@ -0,0 +1,47 @@
+# Pipeline Definitions
+
+Tech debt pipeline modes and task registry.
+
+## Pipeline Modes
+
+| Mode | Description | Task Chain |
+|------|-------------|------------|
+| scan | Scan and assess only, no fixes | TDSCAN-001 -> TDEVAL-001 |
+| remediate | Full pipeline: scan -> assess -> plan -> fix -> validate | TDSCAN-001 -> TDEVAL-001 -> TDPLAN-001 -> TDFIX-001 -> TDVAL-001 |
+| targeted | Skip scan/assess, direct fix path | TDPLAN-001 -> TDFIX-001 -> TDVAL-001 |
+
+## Task Registry
+
+| Task ID | Role | Prefix | blockedBy | Description |
+|---------|------|--------|-----------|-------------|
+| TDSCAN-001 | scanner | TDSCAN | [] | Fan-out multi-dimension codebase scan (code, architecture, testing, dependency, documentation) |
+| TDEVAL-001 | assessor | TDEVAL | [TDSCAN-001] | Severity assessment with priority quadrant matrix |
+| TDPLAN-001 | planner | TDPLAN | [TDEVAL-001] | 3-phase remediation plan with effort estimates |
+| TDFIX-001 | executor | TDFIX | [TDPLAN-001] | Worktree-based incremental fixes (inner_loop: true) |
+| TDVAL-001 | validator | TDVAL | [TDFIX-001] | 4-layer validation: syntax, tests, integration, regression |
+
+## Checkpoints
+
+| Checkpoint | Trigger | Condition | Action |
+|------------|---------|-----------|--------|
+| Plan Approval Gate | TDPLAN-001 completes | Always | ask_question: Approve / Revise / Abort |
+| Worktree Creation | Plan approved | Before TDFIX | git worktree add .worktrees/TD-<slug>-<date> |
+| Fix-Verify GC Loop | TDVAL-* completes | Regressions found | Create TDFIX-fix-<round> + TDVAL-recheck-<round> (max 3 rounds) |
+
+## GC Loop Behavior
+
+| Condition | Action |
+|-----------|--------|
+| No regressions | Pipeline complete |
+| Regressions AND gc_rounds < 3 | Create fix-verify tasks, increment gc_rounds |
+| Regressions AND gc_rounds >= 3 | Accept current state, handleComplete |
+
+## Output Artifacts
+
+| Task | Output Path |
+|------|-------------|
+| TDSCAN-001 | <session>/scan/scan-report.json |
+| TDEVAL-001 | <session>/assessment/debt-assessment.json |
+| TDPLAN-001 | <session>/plan/remediation-plan.md |
+| TDFIX-001 | <session>/fixes/ (worktree) |
+| TDVAL-001 | <session>/validation/validation-report.md |

package/.agy/skills/team-tech-debt/specs/team-config.json

@@ -0,0 +1,129 @@
+{
+  "team_name": "tech-debt",
+  "version": "1.0.0",
+  "description": "技术债务识别与清理团队 - 融合\"债务扫描\"、\"量化评估\"、\"治理规划\"、\"清理执行\"、\"验证回归\"五大能力域，形成扫描→评估→规划→清理→验证的闭环",
+  "skill_entry": "team-tech-debt",
+  "invocation": "Skill(skill=\"team-tech-debt\", args=\"--role=coordinator ...\")",
+
+  "roles": {
+    "coordinator": {
+      "name": "coordinator",
+      "responsibility": "Orchestration",
+      "task_prefix": null,
+      "description": "技术债务治理协调者。编排 pipeline：需求澄清 → 模式选择 → 团队创建 → 任务分发 → 监控协调 → 质量门控 → 结果汇报",
+      "message_types_sent": ["mode_selected", "quality_gate", "task_unblocked", "error", "shutdown"],
+      "message_types_received": ["scan_complete", "assessment_complete", "plan_ready", "fix_complete", "validation_complete", "regression_found", "error"],
+      "commands": ["dispatch", "monitor"]
+    },
+    "scanner": {
+      "name": "scanner",
+      "responsibility": "Orchestration (多维度债务扫描)",
+      "task_prefix": "TDSCAN",
+      "description": "技术债务扫描员。多维度扫描代码库：代码债务、架构债务、测试债务、依赖债务、文档债务，生成债务清单",
+      "message_types_sent": ["scan_complete", "debt_items_found", "error"],
+      "message_types_received": [],
+      "commands": ["scan-debt"],
+      "cli_tools": ["gemini"]
+    },
+    "assessor": {
+      "name": "assessor",
+      "responsibility": "Read-only analysis (量化评估)",
+      "task_prefix": "TDEVAL",
+      "description": "技术债务评估师。量化评估债务项的影响和修复成本，按优先级矩阵排序，生成评估报告",
+      "message_types_sent": ["assessment_complete", "error"],
+      "message_types_received": [],
+      "commands": ["evaluate"],
+      "cli_tools": ["gemini"]
+    },
+    "planner": {
+      "name": "planner",
+      "responsibility": "Orchestration (治理规划)",
+      "task_prefix": "TDPLAN",
+      "description": "技术债务治理规划师。制定分阶段治理方案：短期速赢、中期系统性治理、长期预防机制",
+      "message_types_sent": ["plan_ready", "plan_revision", "error"],
+      "message_types_received": [],
+      "commands": ["create-plan"],
+      "cli_tools": ["gemini"]
+    },
+    "executor": {
+      "name": "executor",
+      "responsibility": "Code generation (债务清理执行)",
+      "task_prefix": "TDFIX",
+      "description": "技术债务清理执行者。按优先级执行重构、依赖更新、代码清理、测试补充等治理动作",
+      "message_types_sent": ["fix_complete", "fix_progress", "error"],
+      "message_types_received": [],
+      "commands": ["remediate"],
+      "cli_tools": [{"tool": "gemini", "mode": "write"}]
+    },
+    "validator": {
+      "name": "validator",
+      "responsibility": "Validation (清理验证)",
+      "task_prefix": "TDVAL",
+      "description": "技术债务清理验证者。验证清理后无回归、质量指标提升、债务确实消除",
+      "message_types_sent": ["validation_complete", "regression_found", "error"],
+      "message_types_received": [],
+      "commands": ["verify"],
+      "cli_tools": [{"tool": "gemini", "mode": "write"}]
+    }
+  },
+
+  "pipeline_modes": {
+    "scan": {
+      "description": "仅扫描评估，不执行修复（审计模式）",
+      "stages": ["TDSCAN", "TDEVAL"],
+      "entry_role": "scanner"
+    },
+    "remediate": {
+      "description": "完整闭环：扫描 → 评估 → 规划 → 修复 → 验证",
+      "stages": ["TDSCAN", "TDEVAL", "TDPLAN", "TDFIX", "TDVAL"],
+      "entry_role": "scanner"
+    },
+    "targeted": {
+      "description": "定向修复：用户已知债务项，直接规划执行",
+      "stages": ["TDPLAN", "TDFIX", "TDVAL"],
+      "entry_role": "planner"
+    }
+  },
+
+  "fix_verify_loop": {
+    "max_iterations": 3,
+    "trigger": "validation fails or regression found",
+    "participants": ["executor", "validator"],
+    "flow": "TDFIX-fix → TDVAL-verify → evaluate"
+  },
+
+  "shared_memory": {
+    "file": ".msg/meta.json",
+    "fields": {
+      "debt_inventory": { "owner": "scanner", "type": "array" },
+      "assessment_matrix": { "owner": "assessor", "type": "object" },
+      "remediation_plan": { "owner": "planner", "type": "object" },
+      "fix_results": { "owner": "executor", "type": "object" },
+      "validation_results": { "owner": "validator", "type": "object" },
+      "debt_score_before": { "owner": "assessor", "type": "number" },
+      "debt_score_after": { "owner": "validator", "type": "number" }
+    }
+  },
+
+  "collaboration_patterns": [
+    "CP-1: Linear Pipeline (scan/remediate/targeted mode)",
+    "CP-2: Review-Fix Cycle (Executor ↔ Validator loop)",
+    "CP-3: Fan-out (Scanner multi-dimension scan)",
+    "CP-5: Escalation (Worker → Coordinator → User)",
+    "CP-6: Incremental Delivery (batch remediation)",
+    "CP-10: Post-Mortem (debt reduction report)"
+  ],
+
+  "debt_dimensions": {
+    "code": { "name": "代码债务", "tools": ["static-analysis", "complexity-metrics"] },
+    "architecture": { "name": "架构债务", "tools": ["dependency-graph", "coupling-analysis"] },
+    "testing": { "name": "测试债务", "tools": ["coverage-analysis", "test-quality"] },
+    "dependency": { "name": "依赖债务", "tools": ["outdated-check", "vulnerability-scan"] },
+    "documentation": { "name": "文档债务", "tools": ["doc-coverage", "api-doc-check"] }
+  },
+
+  "session_directory": {
+    "pattern": ".workflow/.team/TD-{slug}-{date}",
+    "subdirectories": ["scan", "assessment", "plan", "fixes", "validation"]
+  }
+}

package/.agy/skills/team-testing/SKILL.md

@@ -0,0 +1,144 @@
+---
+name: team-testing
+description: Unified team skill for testing team. Progressive test coverage through Generator-Critic loops, shared memory, and dynamic layer selection. Triggers on "team testing".
+allowed-tools:
+  - ask_question
+  - define_subagent
+  - grep_search
+  - invoke_subagent
+  - manage_subagents
+  - replace_file_content
+  - run_command
+  - send_message
+  - view_file
+  - write_to_file
+agy-subagents:
+  - team-worker
+---
+
+## Sub-Agent Registration (Antigravity)
+
+Before any `invoke_subagent` call below, register each sub-agent type once per session by reading the system_prompt from `<agy-agents-dir>/<name>.md` and passing it to `define_subagent`. The `<agy-agents-dir>` is:
+- global install: `~/.gemini/antigravity-cli/agents/`
+- workspace install: `<project>/.agents/agents/`
+
+- `define_subagent(name="team-worker", description="<from agents/team-worker.md frontmatter>", system_prompt=<contents of agents/team-worker.md body>, enable_write_tools=true, enable_mcp_tools=true, enable_subagent_tools=false)`
+
+**ConversationId tracking**: `invoke_subagent` returns a ConversationId per spawned instance. Subsequent `send_message(Recipient=<ConversationId>, Message=...)` calls require that ConversationId — never use the role name as the recipient.
+
+---
+
+# Team Testing
+
+Orchestrate multi-agent test pipeline: strategist -> generator -> executor -> analyst. Progressive layer coverage (L1/L2/L3) with Generator-Critic loops for coverage convergence.
+
+## Architecture
+
+```
+view_file(AbsolutePath="<agy-skills-dir>/team-testing/SKILL.md") + execute inline (args: "task description")
+                    |
+         SKILL.md (this file) = Router
+                    |
+     +--------------+--------------+
+     |                             |
+  no --role flag              --role <name>
+     |                             |
+  Coordinator                  Worker
+  roles/coordinator/role.md    roles/<name>/role.md
+     |
+     +-- analyze -> dispatch -> spawn workers -> STOP
+                                    |
+                    +-------+-------+-------+-------+
+                    v       v       v       v
+                [strat] [gen]  [exec]  [analyst]
+                team-worker agents, each loads roles/<role>/role.md
+```
+
+## Role Registry
+
+| Role | Path | Prefix | Inner Loop |
+|------|------|--------|------------|
+| coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | — | — |
+| strategist | [roles/strategist/role.md](roles/strategist/role.md) | STRATEGY-* | false |
+| generator | [roles/generator/role.md](roles/generator/role.md) | TESTGEN-* | true |
+| executor | [roles/executor/role.md](roles/executor/role.md) | TESTRUN-* | true |
+| analyst | [roles/analyst/role.md](roles/analyst/role.md) | TESTANA-* | false |
+
+## Role Router
+
+Parse `$ARGUMENTS`:
+- Has `--role <name>` -> Read `roles/<name>/role.md`, execute Phase 2-4
+- No `--role` -> `@roles/coordinator/role.md`, execute entry router
+
+## Shared Constants
+
+- **Session prefix**: `TST`
+- **Session path**: `.workflow/.team/TST-<slug>-<date>/`
+- **Team name**: `testing`
+- **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications)
+- **Message bus**: `mcp__ccw-tools__team_msg(session_id=<session-id>, ...)`
+
+## Worker Spawn Template
+
+Coordinator spawns workers using this template:
+
+```
+invoke_subagent([{ TypeName: "team-worker", Role: "<role>", Prompt: "<Prompt>", Workspace: "inherit" }])
+```
+
+## User Commands
+
+| Command | Action |
+|---------|--------|
+| `check` / `status` | View pipeline status graph |
+| `resume` / `continue` | Advance to next step |
+| `revise <TASK-ID>` | Revise specific task |
+| `feedback <text>` | Inject feedback for revision |
+
+## Completion Action
+
+When pipeline completes, coordinator presents:
+
+```
+ask_question({
+  questions: [{
+    question: "Testing pipeline complete. What would you like to do?",
+    header: "Completion",
+    multiSelect: false,
+    options: [
+      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up team" },
+      { label: "Keep Active", description: "Keep session for follow-up work" },
+      { label: "Deepen Coverage", description: "Add more test layers or increase coverage targets" }
+    ]
+  }]
+})
+```
+
+## Session Directory
+
+```
+.workflow/.team/TST-<slug>-<date>/
+├── .msg/messages.jsonl     # Team message bus
+├── .msg/meta.json          # Session metadata
+├── wisdom/                 # Cross-task knowledge
+├── strategy/               # Strategist output
+├── tests/                  # Generator output (L1-unit/, L2-integration/, L3-e2e/)
+├── results/                # Executor output
+└── analysis/               # Analyst output
+```
+
+## Specs Reference
+
+- [specs/pipelines.md](specs/pipelines.md) — Pipeline definitions and task registry
+- [specs/team-config.json](specs/team-config.json) — Team configuration
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Unknown --role value | Error with available role list |
+| Role not found | Error with expected path (roles/<name>/role.md) |
+| CLI tool fails | Worker fallback to direct implementation |
+| GC loop exceeded | Accept current coverage with warning |
+| Fast-advance conflict | Coordinator reconciles on next callback |
+| Completion action fails | Default to Keep Active |

package/.agy/skills/team-testing/roles/analyst/role.md

@@ -0,0 +1,101 @@
+---
+role: analyst
+prefix: TESTANA
+inner_loop: false
+message_types: 
+---
+
+# Test Quality Analyst
+
+Analyze defect patterns, identify coverage gaps, assess GC loop effectiveness, and generate a quality report with actionable recommendations.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Execution results | <session>/results/run-*.json | Yes |
+| Test strategy | <session>/strategy/test-strategy.md | Yes |
+| .msg/meta.json | <session>/wisdom/.msg/meta.json | Yes |
+
+1. Extract session path from task description
+2. Read .msg/meta.json for execution context (executor, generator namespaces)
+3. Read all execution results:
+
+```
+grep_search("<session>/results/run-*.json")
+view_file("<session>/results/run-001.json")
+```
+
+4. Read test strategy:
+
+```
+view_file("<session>/strategy/test-strategy.md")
+```
+
+5. Read test files for pattern analysis:
+
+```
+grep_search("<session>/tests/**/*")
+```
+
+## Phase 3: Quality Analysis
+
+**Analysis dimensions**:
+
+1. **Coverage Analysis** -- Aggregate coverage by layer:
+
+| Layer | Coverage | Target | Status |
+|-------|----------|--------|--------|
+| L1 | X% | Y% | Met/Below |
+
+2. **Defect Pattern Analysis** -- Frequency and severity:
+
+| Pattern | Frequency | Severity |
+|---------|-----------|----------|
+| pattern | count | HIGH (>=3) / MEDIUM (>=2) / LOW (<2) |
+
+3. **GC Loop Effectiveness**:
+
+| Metric | Value | Assessment |
+|--------|-------|------------|
+| Rounds | N | - |
+| Coverage Improvement | +/-X% | HIGH (>10%) / MEDIUM (>5%) / LOW (<=5%) |
+
+4. **Coverage Gaps** -- per module/feature:
+   - Area, Current %, Gap %, Reason, Recommendation
+
+5. **Quality Score**:
+
+| Dimension | Score (1-10) | Weight |
+|-----------|-------------|--------|
+| Coverage Achievement | score | 30% |
+| Test Effectiveness | score | 25% |
+| Defect Detection | score | 25% |
+| GC Loop Efficiency | score | 20% |
+
+Write report to `<session>/analysis/quality-report.md`
+
+### Tech Profile Scan
+
+After test analysis, emit context-aware trigger signals (based on detected codebase characteristics):
+
+1. Check test findings → signals (`test_gap`, `perf_sensitive`)
+2. Check tested code → risk signals (`sql_detected`, `auth_detected`, `injection_risk`)
+3. Include `tech_profile` in Phase 5 state_update data
+
+## Phase 4: Trend Analysis & State Update
+
+**Historical comparison** (if multiple sessions exist):
+
+```
+grep_search(".workflow/.team/TST-*/.msg/meta.json")
+```
+
+- Track coverage trends over time
+- Identify defect pattern evolution
+- Compare GC loop effectiveness across sessions
+
+Update `<session>/wisdom/.msg/meta.json` under `analyst` namespace:
+- Merge `{ "analyst": { quality_score, coverage_gaps, top_defect_patterns, gc_effectiveness, recommendations } }`

package/.agy/skills/team-testing/roles/coordinator/commands/analyze.md

@@ -0,0 +1,70 @@
+# Analyze Task
+
+Parse user task -> detect testing capabilities -> select pipeline -> design roles.
+
+**CONSTRAINT**: Text-level analysis only. NO source code reading, NO codebase exploration.
+
+## Signal Detection
+
+| Keywords | Capability | Prefix |
+|----------|------------|--------|
+| strategy, plan, layers, scope | strategist | STRATEGY |
+| generate tests, write tests, create tests | generator | TESTGEN |
+| run tests, execute, coverage | executor | TESTRUN |
+| analyze, report, quality, defects | analyst | TESTANA |
+
+## Pipeline Mode Detection
+
+| Condition | Pipeline |
+|-----------|----------|
+| fileCount <= 3 AND moduleCount <= 1 | targeted |
+| fileCount <= 10 AND moduleCount <= 3 | standard |
+| Otherwise | comprehensive |
+
+## Dependency Graph
+
+Natural ordering for testing pipeline:
+- Tier 0: strategist (change analysis, no upstream dependency)
+- Tier 1: generator (requires strategy)
+- Tier 2: executor (requires generated tests; GC loop with generator)
+- Tier 3: analyst (requires execution results)
+
+## Pipeline Definitions
+
+```
+Targeted:      STRATEGY -> TESTGEN(L1) -> TESTRUN(L1)
+Standard:      STRATEGY -> TESTGEN(L1) -> TESTRUN(L1) -> TESTGEN(L2) -> TESTRUN(L2) -> TESTANA
+Comprehensive: STRATEGY -> [TESTGEN(L1) || TESTGEN(L2)] -> [TESTRUN(L1) || TESTRUN(L2)] -> TESTGEN(L3) -> TESTRUN(L3) -> TESTANA
+```
+
+## Complexity Scoring
+
+| Factor | Points |
+|--------|--------|
+| Per test layer | +1 |
+| Parallel tracks | +1 per track |
+| GC loop enabled | +1 |
+| Serial depth > 3 | +1 |
+
+Results: 1-2 Low, 3-5 Medium, 6+ High
+
+## Role Minimization
+
+- Cap at 5 roles (coordinator + 4 workers)
+- GC loop: generator <-> executor iterate up to 3 rounds per layer
+
+## Output
+
+Write <session>/task-analysis.json:
+```json
+{
+  "task_description": "<original>",
+  "pipeline_mode": "<targeted|standard|comprehensive>",
+  "capabilities": [{ "name": "<cap>", "prefix": "<PREFIX>", "keywords": ["..."] }],
+  "dependency_graph": { "<TASK-ID>": { "role": "<role>", "blockedBy": ["..."], "layer": "L1|L2|L3" } },
+  "roles": [{ "name": "<role>", "prefix": "<PREFIX>", "inner_loop": true }],
+  "complexity": { "score": 0, "level": "Low|Medium|High" },
+  "coverage_targets": { "L1": 80, "L2": 60, "L3": 40 },
+  "gc_loop_enabled": true
+}
+```