mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-10 17:11:04 +08:00
29a1fea467
- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files. - Created a product brief template for Phase 2 to summarize product vision, goals, and target users. - Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices. feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis - Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt. - Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
3.0 KiB
3.0 KiB
role, prefix, inner_loop, message_types
| role | prefix | inner_loop | message_types | ||||
|---|---|---|---|---|---|---|---|
| explorer | EXPLORE | false |
|
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 |
- 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" |
- Determine exploration number from task subject (EXPLORE-N)
- 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:
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):
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