mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-05 16:13:08 +08:00
fd847070d5
- 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.
75 lines
3.0 KiB
Markdown
75 lines
3.0 KiB
Markdown
---
|
|
prefix: EXPLORE
|
|
inner_loop: false
|
|
subagents: []
|
|
message_types:
|
|
success: exploration_ready
|
|
error: error
|
|
---
|
|
|
|
# Codebase Explorer
|
|
|
|
Explore codebase structure through cli-explore-agent, collecting structured context (files, patterns, findings) for downstream analysis. One explorer per analysis perspective.
|
|
|
|
## Phase 2: Context & Scope Assessment
|
|
|
|
| Input | Source | Required |
|
|
|-------|--------|----------|
|
|
| Task description | From task subject/description | Yes |
|
|
| Session path | Extracted from task description | Yes |
|
|
|
|
1. Extract session path, topic, perspective, dimensions from task description:
|
|
|
|
| Field | Pattern | Default |
|
|
|-------|---------|---------|
|
|
| sessionFolder | `session:\s*(.+)` | required |
|
|
| topic | `topic:\s*(.+)` | required |
|
|
| perspective | `perspective:\s*(.+)` | "general" |
|
|
| dimensions | `dimensions:\s*(.+)` | "general" |
|
|
|
|
2. Determine exploration number from task subject (EXPLORE-N)
|
|
3. Build exploration strategy by perspective:
|
|
|
|
| Perspective | Focus | Search Depth |
|
|
|-------------|-------|-------------|
|
|
| general | Overall codebase structure and patterns | broad |
|
|
| technical | Implementation details, code patterns, feasibility | medium |
|
|
| architectural | System design, module boundaries, interactions | broad |
|
|
| business | Business logic, domain models, value flows | medium |
|
|
| domain_expert | Domain patterns, standards, best practices | deep |
|
|
|
|
## Phase 3: Codebase Exploration
|
|
|
|
Use CLI tool for codebase exploration:
|
|
|
|
```javascript
|
|
Bash({
|
|
command: `ccw cli -p "PURPOSE: Explore codebase for <topic> from <perspective> perspective; success = structured findings with relevant files and patterns
|
|
TASK: • Run module depth analysis • Search for topic-related patterns • Identify key files and their relationships • Extract architectural insights
|
|
MODE: analysis
|
|
CONTEXT: @**/* | Memory: Session <session-folder>, perspective <perspective>
|
|
EXPECTED: JSON output with: relevant_files (path, relevance, summary), patterns, key_findings, module_map, questions_for_analysis, _metadata (perspective, search_queries, timestamp)
|
|
CONSTRAINTS: Focus on <perspective> angle - <strategy.focus> | Write to <session>/explorations/exploration-<num>.json
|
|
" --tool gemini --mode analysis --rule analysis-analyze-code-patterns`,
|
|
run_in_background: false
|
|
})
|
|
```
|
|
|
|
**ACE fallback** (when CLI produces no output):
|
|
```javascript
|
|
mcp__ace-tool__search_context({ project_root_path: ".", query: "<topic> <perspective>" })
|
|
```
|
|
|
|
## Phase 4: Result Validation
|
|
|
|
| Check | Method | Action on Failure |
|
|
|-------|--------|-------------------|
|
|
| Output file exists | Read output path | Create empty result, run ACE fallback |
|
|
| Has relevant_files | Array length > 0 | Trigger ACE supplementary search |
|
|
| Has key_findings | Array length > 0 | Note partial results, proceed |
|
|
|
|
Write validated exploration to `<session>/explorations/exploration-<num>.json`.
|
|
|
|
Update `<session>/wisdom/.msg/meta.json` under `explorer` namespace:
|
|
- Read existing -> merge `{ "explorer": { perspective, file_count, finding_count } }` -> write back
|