claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-tech-debt/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-tech-debt
 description: Unified team skill for tech debt identification and remediation. Scans codebase for tech debt, assesses severity, plans and executes fixes with validation. Uses team-worker agent architecture with roles/ for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team tech debt".
-allowed-tools: spawn_agent(*), wait_agent(*), send_input(*), close_agent(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ace-tool__search_context(*), mcp__ccw-tools__read_file(*), mcp__ccw-tools__write_file(*), mcp__ccw-tools__edit_file(*), mcp__ccw-tools__team_msg(*)
+allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), assign_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ace-tool__search_context(*), mcp__ccw-tools__read_file(*), mcp__ccw-tools__write_file(*), mcp__ccw-tools__edit_file(*), mcp__ccw-tools__team_msg(*)
 ---
 
 # Team Tech Debt
@@ -55,7 +55,8 @@ Before calling ANY tool, apply this check:
 
 | Tool Call | Verdict | Reason |
 |-----------|---------|--------|
-| `spawn_agent`, `wait_agent`, `close_agent`, `send_input` | ALLOWED | Orchestration |
+| `spawn_agent`, `wait_agent`, `close_agent`, `send_message`, `assign_task` | ALLOWED | Orchestration |
+| `list_agents` | ALLOWED | Agent health check |
 | `request_user_input` | ALLOWED | User interaction |
 | `mcp__ccw-tools__team_msg` | ALLOWED | Message bus |
 | `Read/Write` on `.workflow/.team/` files | ALLOWED | Session state |
@@ -86,6 +87,8 @@ Coordinator spawns workers using this template:
 ```
 spawn_agent({
   agent_type: "team_worker",
+  task_name: "<task-id>",
+  fork_context: false,
   items: [
     { type: "text", text: `## Role Assignment
 role: <role>
@@ -109,7 +112,29 @@ pipeline_phase: <pipeline-phase>` },
 })
 ```
 
-After spawning, use `wait_agent({ ids: [...], timeout_ms: 900000 })` to collect results, then `close_agent({ id })` each worker.
+After spawning, use `wait_agent({ targets: [...], timeout_ms: 900000 })` to collect results, then `close_agent({ target })` each worker.
+
+
+### Model Selection Guide
+
+Tech debt follows a discovery-to-fix pipeline. Scanner is broad/fast, later stages need deeper reasoning.
+
+| Role | reasoning_effort | Rationale |
+|------|-------------------|-----------|
+| scanner | medium | Broad codebase scan, pattern matching over deep analysis |
+| assessor | high | Severity assessment requires understanding impact and risk |
+| planner | high | Remediation planning must prioritize and sequence fixes |
+| executor | high | Code fixes must preserve behavior while removing debt |
+| validator | medium | Validation follows defined acceptance criteria |
+
+### Pipeline Pattern: Scanner Results Inform Downstream
+
+Scanner discoveries flow through the pipeline — each stage narrows and refines:
+1. TDSCAN produces broad debt inventory
+2. TDEVAL assesses and prioritizes (filters low-impact items)
+3. TDPLAN creates sequenced fix plan from assessed items
+4. TDFIX implements fixes per plan
+5. TDVAL validates fixes against original debt findings
 
 ## User Commands
 
@@ -141,6 +166,34 @@ After spawning, use `wait_agent({ ids: [...], timeout_ms: 900000 })` to collect
 └── wisdom/                 # Cross-task knowledge
 ```
 
+## v4 Agent Coordination
+
+### Message Semantics
+
+| Intent | API | Example |
+|--------|-----|---------|
+| Queue supplementary info (don't interrupt) | `send_message` | Send scan findings to running assessor |
+| Assign fix from remediation plan | `assign_task` | Assign TDFIX task from planner output |
+| Check running agents | `list_agents` | Verify agent health during resume |
+
+### Agent Health Check
+
+Use `list_agents({})` in handleResume and handleComplete:
+
+```
+// Reconcile session state with actual running agents
+const running = list_agents({})
+// Compare with meta.json active tasks
+// Reset orphaned tasks (in_progress but agent gone) to pending
+```
+
+### Named Agent Targeting
+
+Workers are spawned with `task_name: "<task-id>"` enabling direct addressing:
+- `send_message({ target: "TDSCAN-001", items: [...] })` -- send additional scan scope to scanner
+- `assign_task({ target: "TDFIX-001", items: [...] })` -- assign fix task from planner output
+- `close_agent({ target: "TDVAL-001" })` -- cleanup after validation
+
 ## Error Handling
 
 | Scenario | Resolution |

package/.codex/skills/team-tech-debt/roles/assessor/role.md

@@ -1,69 +1,69 @@
----
-role: assessor
-prefix: TDEVAL
-inner_loop: false
-message_types: [state_update]
----
-
-# Tech Debt Assessor
-
-Quantitative evaluator for tech debt items. Score each debt item on business impact (1-5) and fix cost (1-5), classify into priority quadrants, produce priority-matrix.json.
-
-## Phase 2: Load Debt Inventory
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session path | task description (regex: `session:\s*(.+)`) | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-| Debt inventory | meta.json:debt_inventory OR <session>/scan/debt-inventory.json | Yes |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for team context
-3. Load debt_inventory from shared memory or fallback to debt-inventory.json file
-4. If debt_inventory is empty -> report empty assessment and exit
-
-## Phase 3: Evaluate Each Item
-
-**Strategy selection**:
-
-| Item Count | Strategy |
-|------------|----------|
-| <= 10 | Heuristic: severity-based impact + effort-based cost |
-| 11-50 | CLI batch: single gemini analysis call |
-| > 50 | CLI chunked: batches of 25 items |
-
-**Impact Score Mapping** (heuristic):
-
-| Severity | Impact Score |
-|----------|-------------|
-| critical | 5 |
-| high | 4 |
-| medium | 3 |
-| low | 1 |
-
-**Cost Score Mapping** (heuristic):
-
-| Estimated Effort | Cost Score |
-|------------------|------------|
-| small | 1 |
-| medium | 3 |
-| large | 5 |
-| unknown | 3 |
-
-**Priority Quadrant Classification**:
-
-| Impact | Cost | Quadrant |
-|--------|------|----------|
-| >= 4 | <= 2 | quick-win |
-| >= 4 | >= 3 | strategic |
-| <= 3 | <= 2 | backlog |
-| <= 3 | >= 3 | defer |
-
-For CLI mode, prompt gemini with full debt summary requesting JSON array of `{id, impact_score, cost_score, risk_if_unfixed, priority_quadrant}`. Unevaluated items fall back to heuristic scoring.
-
-## Phase 4: Generate Priority Matrix
-
-1. Build matrix structure: evaluation_date, total_items, by_quadrant (grouped), summary (counts per quadrant)
-2. Sort within each quadrant by impact_score descending
-3. Write `<session>/assessment/priority-matrix.json`
-4. Update .msg/meta.json with `priority_matrix` summary and evaluated `debt_inventory`
+---
+role: assessor
+prefix: TDEVAL
+inner_loop: false
+message_types: [state_update]
+---
+
+# Tech Debt Assessor
+
+Quantitative evaluator for tech debt items. Score each debt item on business impact (1-5) and fix cost (1-5), classify into priority quadrants, produce priority-matrix.json.
+
+## Phase 2: Load Debt Inventory
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Session path | task description (regex: `session:\s*(.+)`) | Yes |
+| .msg/meta.json | <session>/.msg/meta.json | Yes |
+| Debt inventory | meta.json:debt_inventory OR <session>/scan/debt-inventory.json | Yes |
+
+1. Extract session path from task description
+2. Read .msg/meta.json for team context
+3. Load debt_inventory from shared memory or fallback to debt-inventory.json file
+4. If debt_inventory is empty -> report empty assessment and exit
+
+## Phase 3: Evaluate Each Item
+
+**Strategy selection**:
+
+| Item Count | Strategy |
+|------------|----------|
+| <= 10 | Heuristic: severity-based impact + effort-based cost |
+| 11-50 | CLI batch: single gemini analysis call |
+| > 50 | CLI chunked: batches of 25 items |
+
+**Impact Score Mapping** (heuristic):
+
+| Severity | Impact Score |
+|----------|-------------|
+| critical | 5 |
+| high | 4 |
+| medium | 3 |
+| low | 1 |
+
+**Cost Score Mapping** (heuristic):
+
+| Estimated Effort | Cost Score |
+|------------------|------------|
+| small | 1 |
+| medium | 3 |
+| large | 5 |
+| unknown | 3 |
+
+**Priority Quadrant Classification**:
+
+| Impact | Cost | Quadrant |
+|--------|------|----------|
+| >= 4 | <= 2 | quick-win |
+| >= 4 | >= 3 | strategic |
+| <= 3 | <= 2 | backlog |
+| <= 3 | >= 3 | defer |
+
+For CLI mode, prompt gemini with full debt summary requesting JSON array of `{id, impact_score, cost_score, risk_if_unfixed, priority_quadrant}`. Unevaluated items fall back to heuristic scoring.
+
+## Phase 4: Generate Priority Matrix
+
+1. Build matrix structure: evaluation_date, total_items, by_quadrant (grouped), summary (counts per quadrant)
+2. Sort within each quadrant by impact_score descending
+3. Write `<session>/assessment/priority-matrix.json`
+4. Update .msg/meta.json with `priority_matrix` summary and evaluated `debt_inventory`

package/.codex/skills/team-tech-debt/roles/coordinator/commands/analyze.md

@@ -1,47 +1,47 @@
-# Analyze Task
-
-Parse user task -> detect tech debt signals -> assess complexity -> determine pipeline mode and roles.
-
-**CONSTRAINT**: Text-level analysis only. NO source code reading, NO codebase exploration.
-
-## Signal Detection
-
-| Keywords | Signal | Mode Hint |
-|----------|--------|-----------|
-| 扫描, scan, 审计, audit | debt-scan | scan |
-| 评估, assess, quantify | debt-assess | scan |
-| 规划, plan, roadmap | debt-plan | targeted |
-| 修复, fix, remediate, clean | debt-fix | remediate |
-| 验证, validate, verify | debt-validate | remediate |
-| 定向, targeted, specific | debt-targeted | targeted |
-
-## Complexity Scoring
-
-| Factor | Points |
-|--------|--------|
-| Full codebase scope | +2 |
-| Multiple debt dimensions | +1 per dimension (max 3) |
-| Large codebase (implied) | +1 |
-| Targeted specific items | -1 |
-
-Results: 1-3 Low (scan mode), 4-6 Medium (remediate), 7+ High (remediate + full pipeline)
-
-## Pipeline Mode Determination
-
-| Score + Signals | Mode |
-|----------------|------|
-| scan/audit keywords | scan |
-| targeted/specific keywords | targeted |
-| Default | remediate |
-
-## Output
-
-Write scope context to coordinator memory:
-```json
-{
-  "pipeline_mode": "<scan|remediate|targeted>",
-  "scope": "<detected-scope>",
-  "focus_dimensions": ["code", "architecture", "testing", "dependency", "documentation"],
-  "complexity": { "score": 0, "level": "Low|Medium|High" }
-}
-```
+# Analyze Task
+
+Parse user task -> detect tech debt signals -> assess complexity -> determine pipeline mode and roles.
+
+**CONSTRAINT**: Text-level analysis only. NO source code reading, NO codebase exploration.
+
+## Signal Detection
+
+| Keywords | Signal | Mode Hint |
+|----------|--------|-----------|
+| 扫描, scan, 审计, audit | debt-scan | scan |
+| 评估, assess, quantify | debt-assess | scan |
+| 规划, plan, roadmap | debt-plan | targeted |
+| 修复, fix, remediate, clean | debt-fix | remediate |
+| 验证, validate, verify | debt-validate | remediate |
+| 定向, targeted, specific | debt-targeted | targeted |
+
+## Complexity Scoring
+
+| Factor | Points |
+|--------|--------|
+| Full codebase scope | +2 |
+| Multiple debt dimensions | +1 per dimension (max 3) |
+| Large codebase (implied) | +1 |
+| Targeted specific items | -1 |
+
+Results: 1-3 Low (scan mode), 4-6 Medium (remediate), 7+ High (remediate + full pipeline)
+
+## Pipeline Mode Determination
+
+| Score + Signals | Mode |
+|----------------|------|
+| scan/audit keywords | scan |
+| targeted/specific keywords | targeted |
+| Default | remediate |
+
+## Output
+
+Write scope context to coordinator memory:
+```json
+{
+  "pipeline_mode": "<scan|remediate|targeted>",
+  "scope": "<detected-scope>",
+  "focus_dimensions": ["code", "architecture", "testing", "dependency", "documentation"],
+  "complexity": { "score": 0, "level": "Low|Medium|High" }
+}
+```