Files
Claude-Code-Workflow/.claude/skills/team-issue/role-specs/planner.md
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

2.7 KiB

prefix, inner_loop, additional_prefixes, subagents, message_types
prefix inner_loop additional_prefixes subagents message_types
SOLVE false
SOLVE-fix
issue-plan-agent
success multi error
solution_ready multi_solution error

Issue Planner

Design solutions and decompose into implementation tasks. Internally invokes issue-plan-agent for ACE exploration and solution generation. For revision tasks (SOLVE-fix), design alternative approaches addressing reviewer feedback.

Phase 2: Context Loading

Input Source Required
Issue ID Task description (GH-\d+ or ISS-\d{8}-\d{6}) Yes
Explorer context <session>/explorations/context-<issueId>.json No
Review feedback Task description (for SOLVE-fix tasks) No
.msg/meta.json /wisdom/.msg/meta.json No
  1. Extract issue ID from task description via regex: (?:GH-\d+|ISS-\d{8}-\d{6})
  2. If no issue ID found -> report error, STOP
  3. Load explorer context report (if available):
Read("<session>/explorations/context-<issueId>.json")
  1. Check if this is a revision task (SOLVE-fix-N):
    • If yes, extract reviewer feedback from task description
    • Design alternative approach addressing reviewer concerns
  2. Load wisdom files for accumulated codebase knowledge

Phase 3: Solution Generation via issue-plan-agent

Agent invocation:

Agent({
  subagent_type: "issue-plan-agent",
  run_in_background: false,
  description: "Plan solution for <issueId>",
  prompt: "
issue_ids: [\"<issueId>\"]
project_root: \"<projectRoot>\"

## Explorer Context (pre-gathered)
Relevant files: <explorerContext.relevant_files>
Key findings: <explorerContext.key_findings>
Complexity: <explorerContext.complexity_assessment>

## Revision Required (if SOLVE-fix)
Previous solution was rejected by reviewer. Feedback:
<reviewFeedback>

Design an ALTERNATIVE approach that addresses the reviewer's concerns.
"
})

Expected agent result:

Field Description
bound Array of auto-bound solutions: [{issue_id, solution_id, task_count}]
pending_selection Array of multi-solution issues: [{issue_id, solutions: [...]}]

Phase 4: Solution Selection & Reporting

Outcome routing:

Condition Message Type Action
Single solution auto-bound solution_ready Report to coordinator
Multiple solutions pending multi_solution Report for user selection
No solution generated error Report failure to coordinator

Write solution summary to <session>/solutions/solution-<issueId>.json.

Update <session>/wisdom/.msg/meta.json under planner namespace:

  • Read existing -> merge { "planner": { issue_id, solution_id, task_count, is_revision } } -> write back