mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-06 16:31:12 +08:00
16bbfcd12a
## 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/
91 lines
3.1 KiB
Markdown
91 lines
3.1 KiB
Markdown
---
|
|
prefix: EXPLORE
|
|
inner_loop: false
|
|
subagents: [cli-explore-agent]
|
|
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
|
|
|
|
Spawn `cli-explore-agent` subagent for actual exploration:
|
|
|
|
```
|
|
Agent({
|
|
subagent_type: "cli-explore-agent",
|
|
run_in_background: false,
|
|
description: "Explore codebase: <topic> (<perspective>)",
|
|
prompt: `
|
|
## Analysis Context
|
|
Topic: <topic>
|
|
Perspective: <perspective> -- <strategy.focus>
|
|
Dimensions: <dimensions>
|
|
Session: <session-folder>
|
|
|
|
## MANDATORY FIRST STEPS
|
|
1. Run: ccw tool exec get_modules_by_depth '{}'
|
|
2. Execute searches based on topic + perspective keywords
|
|
3. Run: ccw spec load --category exploration
|
|
|
|
## Exploration Focus (<perspective> angle)
|
|
<dimension-specific exploration instructions>
|
|
|
|
## Output
|
|
Write findings to: <session>/explorations/exploration-<num>.json
|
|
Schema: { perspective, relevant_files: [{path, relevance, summary}], patterns: [string],
|
|
key_findings: [string], module_map: {module: [files]}, questions_for_analysis: [string],
|
|
_metadata: {agent, perspective, search_queries, timestamp} }
|
|
`
|
|
})
|
|
```
|
|
|
|
**ACE fallback** (when cli-explore-agent produces no output):
|
|
```
|
|
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
|