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

Files

catlog22 fd847070d5 Refactor architecture optimization and issue resolution workflows

- Enhanced multi-perspective discussion capabilities in discuss-subagent for architecture optimization, integrating CLI tools for structured analysis and recommendations.
- Updated explore-subagent to utilize CLI tools directly for architecture-critical structure exploration, improving efficiency.
- Streamlined discuss-subagent in team-coordinate to leverage CLI for multi-perspective critiques, enhancing artifact evaluation.
- Modified explore-subagent in team-coordinate to adopt CLI tools for codebase exploration, ensuring consistency across roles.
- Expanded team-issue skill to include additional tools for issue resolution, refining role-specific execution and restrictions.
- Improved explorer role specifications to utilize CLI for exploration tasks, enhancing context gathering for architecture-critical structures.
- Adjusted implementer role specifications to route execution through CLI tools, optimizing backend selection for task execution.
- Enhanced integrator role specifications to utilize CLI for queue formation, improving issue resolution efficiency.
- Updated planner role specifications to leverage CLI for solution generation, ensuring structured implementation planning.
- Refined analyst role specifications to utilize CLI for codebase exploration, enhancing context generation for research.
- Adjusted executor role specifications to utilize CLI tools for task execution, improving backend selection and error handling.
- Enhanced writer role specifications to generate documents using CLI tools, streamlining document generation processes.
- Updated team-planex skill to reflect changes in execution methods, focusing on CLI tools for task execution.
- Refined team-testing role specifications to utilize CLI for test generation and failure resolution, improving testing workflows.
- Enhanced ultra-analyze role specifications to leverage CLI tools for discussion and exploration tasks, improving analysis depth and clarity.

2026-03-04 23:19:36 +08:00

3.6 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	CLI exploration: `Bash("ccw cli -p \"<exploration_prompt>\" --tool gemini --mode analysis", { run_in_background: false })`

CLI exploration prompt template:

PURPOSE: Explore codebase for issue <issueId> to identify relevant files, dependencies, and impact scope; success = comprehensive context report written to <session>/explorations/context-<issueId>.json

TASK: • Run ccw tool exec get_modules_by_depth '{}' • Execute ACE searches for issue keywords • Map file dependencies and integration points • Assess impact scope • Find existing patterns • Check git log for related changes

MODE: analysis

CONTEXT: @**/* | Memory: Issue <issueId> - <issue.title> (Priority: <issue.priority>)

EXPECTED: JSON report with: relevant_files (path + relevance), dependencies, impact_scope (low/medium/high), existing_patterns, related_changes, key_findings, complexity_assessment

CONSTRAINTS: Focus on issue context | Write output 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.6 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.6 KiB

Raw Blame History