Files
Claude-Code-Workflow/.claude/skills/team-issue/role-specs/planner.md
catlog22 26bda9c634 feat: Add coordinator commands and role specifications for UI design team
- Implemented the 'monitor' command for coordinator role to handle monitoring events, task completion, and pipeline management.
- Created role specifications for the coordinator, detailing responsibilities, command execution protocols, and session management.
- Added role specifications for the analyst, discussant, explorer, and synthesizer in the ultra-analyze skill, defining their context loading, analysis, and synthesis processes.
2026-03-03 23:35:41 +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:

Task({
  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