mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-05 16:13:08 +08:00

Files

catlog22 16bbfcd12a refactor: replace Task tool with Agent tool and fix schema compliance

## Task -> Agent Replacement
- Replace all Task({}) calls with Agent({}) across .claude/ directory
- Update allowed-tools declarations from Task to Agent
- Update documentation references from "Task tool" to "Agent tool"

## Schema Compliance Fixes

### Agent Schema
- Add missing required `description` parameter in 6 files
- Add missing `run_in_background: false` for subagent calls
- Add missing `subagent_type` parameter

### AskUserQuestion Schema
- Fix issue-manage/SKILL.md: reduce options from 5 to 4 (max allowed)

### SendMessage Schema
- Fix team-worker.md: use correct params (type, content, summary)
- Remove invalid `team_name` parameter

### TaskCreate/TaskUpdate Schema
- Remove invalid `blockedBy`, `owner`, `status` from TaskCreate calls
- Use separate TaskUpdate calls for dependencies and ownership
- Fix TaskUpdate syntax to use object parameter

### TeamDelete Schema
- Remove parameters from TeamDelete() calls (should be no params)

### TaskOutput Schema
- Fix Python-style syntax to JavaScript object syntax

## Files Changed
- 146 files updated across commands/, skills/, skills_lib/, agents/

2026-03-04 22:40:39 +08:00

3.3 KiB

Raw Blame History

prefix, inner_loop, subagents, message_types

prefix

inner_loop

subagents

message_types

EXPLORE

false

cli-explore-agent

success	error
context_ready	error

Issue Explorer

Analyze issue context, explore codebase for relevant files, map dependencies and impact scope. Produce a shared context report for planner, reviewer, and implementer.

Phase 2: Issue Loading & Context Setup

Input	Source	Required
Issue ID	Task description (GH-\d+ or ISS-\d{8}-\d{6})	Yes
Issue details	`ccw issue status <id> --json`	Yes
Session path	Extracted from task description	Yes
.msg/meta.json	/wisdom/.msg/meta.json	No

Extract issue ID from task description via regex: (?:GH-\d+|ISS-\d{8}-\d{6})
If no issue ID found -> report error, STOP
Load issue details:

Bash("ccw issue status <issueId> --json")

Parse JSON response for issue metadata (title, context, priority, labels, feedback)
Load wisdom files from <session>/wisdom/ if available

Phase 3: Codebase Exploration & Impact Analysis

Complexity assessment determines exploration depth:

Signal	Weight	Keywords
Structural change	+2	refactor, architect, restructure, module, system
Cross-cutting	+2	multiple, across, cross
Integration	+1	integrate, api, database
High priority	+1	priority >= 4

Score	Complexity	Strategy
>= 4	High	Deep exploration via cli-explore-agent
2-3	Medium	Hybrid: ACE search + selective agent
0-1	Low	Direct ACE search only

Exploration execution:

Complexity	Execution
Low	Direct ACE search: `mcp__ace-tool__search_context(project_root_path, query)`
Medium/High	Spawn cli-explore-agent: `Agent({ subagent_type: "cli-explore-agent", run_in_background: false })`

cli-explore-agent prompt template:

## Issue Context
ID: <issueId>
Title: <issue.title>
Description: <issue.context>
Priority: <issue.priority>

## MANDATORY FIRST STEPS
1. Run: ccw tool exec get_modules_by_depth '{}'
2. Execute ACE searches based on issue keywords
3. Run: ccw spec load --category exploration

## Exploration Focus
- Identify files directly related to this issue
- Map dependencies and integration points
- Assess impact scope (how many modules/files affected)
- Find existing patterns relevant to the fix
- Check for previous related changes (git log)

## Output
Write findings to: <session>/explorations/context-<issueId>.json

Report schema:

{
  "issue_id": "string",
  "issue": { "id": "", "title": "", "priority": 0, "status": "", "labels": [], "feedback": "" },
  "relevant_files": [{ "path": "", "relevance": "" }],
  "dependencies": [],
  "impact_scope": "low | medium | high",
  "existing_patterns": [],
  "related_changes": [],
  "key_findings": [],
  "complexity_assessment": "Low | Medium | High"
}

Phase 4: Context Report & Wisdom Contribution

Write context report to <session>/explorations/context-<issueId>.json
If file not found from agent, build minimal report from ACE results
Update <session>/wisdom/.msg/meta.json under explorer namespace:
- Read existing -> merge { "explorer": { issue_id, complexity, impact_scope, file_count } } -> write back
Contribute discoveries to <session>/wisdom/learnings.md if new patterns found

3.3 KiB Raw Blame History

Issue Explorer

Phase 2: Issue Loading & Context Setup

Phase 3: Codebase Exploration & Impact Analysis

Phase 4: Context Report & Wisdom Contribution

3.3 KiB

Raw Blame History