mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-26 19:56:37 +08:00
1e560ab8e8
- Delete 21 old team skill directories using CSV-wave pipeline pattern (~100+ files) - Delete old team-lifecycle (v3) and team-planex-v2 - Create generic team-worker.toml and team-supervisor.toml (replacing tlv4-specific TOMLs) - Convert 19 team skills from Claude Code format (Agent/SendMessage/TaskCreate) to Codex format (spawn_agent/wait_agent/tasks.json/request_user_input) - Update team-lifecycle-v4 to use generic agent types (team_worker/team_supervisor) - Convert all coordinator role files: dispatch.md, monitor.md, role.md - Convert all worker role files: remove run_in_background, fix Bash syntax - Convert all specs/pipelines.md references - Final state: 20 team skills, 217 .md files, zero Claude Code API residuals Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.9 KiB
2.9 KiB
role, prefix, inner_loop, additional_prefixes, message_types
| role | prefix | inner_loop | additional_prefixes | message_types | ||||
|---|---|---|---|---|---|---|---|---|
| planner | SOLVE | false |
|
|
Issue Planner
Design solutions and decompose into implementation tasks. Uses CLI tools 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 |
| wisdom meta | /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 explorer context report (if available):
Read("<session>/explorations/context-<issueId>.json")
- Check if this is a revision task (SOLVE-fix-N):
- If yes, extract reviewer feedback from task description
- Design alternative approach addressing reviewer concerns
- Load wisdom files for accumulated codebase knowledge
Phase 3: Solution Generation via CLI
CLI invocation:
Bash("ccw cli -p \"
PURPOSE: Design solution for issue <issueId> and decompose into implementation tasks; success = solution bound to issue with task breakdown
TASK: * Load issue details from ccw issue status * Analyze explorer context * Design solution approach * Break down into implementation tasks * Generate solution JSON * Bind solution to issue
MODE: analysis
CONTEXT: @**/* | Memory: Issue <issueId> - <issue.title> (Priority: <issue.priority>)
Explorer findings: <explorerContext.key_findings>
Relevant files: <explorerContext.relevant_files>
Complexity: <explorerContext.complexity_assessment>
EXPECTED: Solution JSON with: issue_id, solution_id, approach, tasks (ordered list with descriptions), estimated_files, dependencies
Write to: <session>/solutions/solution-<issueId>.json
Then bind: ccw issue bind <issueId> <solution_id>
CONSTRAINTS: Follow existing patterns | Minimal changes | Address reviewer feedback if SOLVE-fix task
\" --tool gemini --mode analysis")
Expected CLI output: Solution file path and binding confirmation
Parse result:
Read("<session>/solutions/solution-<issueId>.json")
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