mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-05 16:13:08 +08:00
- 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.
108 lines
3.9 KiB
Markdown
108 lines
3.9 KiB
Markdown
---
|
|
prefix: DISCUSS
|
|
inner_loop: false
|
|
subagents: []
|
|
message_types:
|
|
success: discussion_processed
|
|
error: error
|
|
---
|
|
|
|
# Discussant
|
|
|
|
Process analysis results and user feedback. Execute direction adjustments, deep-dive explorations, or targeted Q&A based on discussion type. Update discussion timeline.
|
|
|
|
## Phase 2: Context Loading
|
|
|
|
| Input | Source | Required |
|
|
|-------|--------|----------|
|
|
| Task description | From task subject/description | Yes |
|
|
| Session path | Extracted from task description | Yes |
|
|
| Analysis results | `<session>/analyses/*.json` | Yes |
|
|
| Exploration results | `<session>/explorations/*.json` | No |
|
|
|
|
1. Extract session path, topic, round, discussion type, user feedback:
|
|
|
|
| Field | Pattern | Default |
|
|
|-------|---------|---------|
|
|
| sessionFolder | `session:\s*(.+)` | required |
|
|
| topic | `topic:\s*(.+)` | required |
|
|
| round | `round:\s*(\d+)` | 1 |
|
|
| discussType | `type:\s*(.+)` | "initial" |
|
|
| userFeedback | `user_feedback:\s*(.+)` | empty |
|
|
|
|
2. Read all analysis and exploration results
|
|
3. Aggregate current findings, insights, open questions
|
|
|
|
## Phase 3: Discussion Processing
|
|
|
|
Select strategy by discussion type:
|
|
|
|
| Type | Mode | Description |
|
|
|------|------|-------------|
|
|
| initial | inline | Aggregate all analyses: convergent themes, conflicts, top discussion points |
|
|
| deepen | subagent | Spawn cli-explore-agent to investigate open questions deeper |
|
|
| direction-adjusted | cli | Re-analyze via `ccw cli` from adjusted perspective |
|
|
| specific-questions | subagent | Targeted exploration answering user questions |
|
|
|
|
**initial**: Cross-perspective summary -- identify convergent themes, conflicting views, top 5 discussion points and open questions from all analyses.
|
|
|
|
**deepen**: Use CLI tool for deep investigation:
|
|
```javascript
|
|
Bash({
|
|
command: `ccw cli -p "PURPOSE: Investigate open questions and uncertain insights; success = evidence-based findings
|
|
TASK: • Focus on open questions: <questions> • Find supporting evidence • Validate uncertain insights • Document findings
|
|
MODE: analysis
|
|
CONTEXT: @**/* | Memory: Session <session-folder>, previous analyses
|
|
EXPECTED: JSON output with investigation results | Write to <session>/discussions/deepen-<num>.json
|
|
CONSTRAINTS: Evidence-based analysis only
|
|
" --tool gemini --mode analysis --rule analysis-trace-code-execution`,
|
|
run_in_background: false
|
|
})
|
|
```
|
|
|
|
**direction-adjusted**: CLI re-analysis from adjusted focus:
|
|
```javascript
|
|
Bash({
|
|
command: `ccw cli -p "Re-analyze '<topic>' with adjusted focus on '<userFeedback>'" --tool gemini --mode analysis`,
|
|
run_in_background: false
|
|
})
|
|
```
|
|
|
|
**specific-questions**: Use CLI tool for targeted Q&A:
|
|
```javascript
|
|
Bash({
|
|
command: `ccw cli -p "PURPOSE: Answer specific user questions about <topic>; success = clear, evidence-based answers
|
|
TASK: • Answer: <userFeedback> • Provide code references • Explain context
|
|
MODE: analysis
|
|
CONTEXT: @**/* | Memory: Session <session-folder>
|
|
EXPECTED: JSON output with answers and evidence | Write to <session>/discussions/questions-<num>.json
|
|
CONSTRAINTS: Direct answers with code references
|
|
" --tool gemini --mode analysis`,
|
|
run_in_background: false
|
|
})
|
|
```
|
|
|
|
## Phase 4: Update Discussion Timeline
|
|
|
|
1. Write round content to `<session>/discussions/discussion-round-<num>.json`:
|
|
```json
|
|
{
|
|
"round": 1, "type": "initial", "user_feedback": "...",
|
|
"updated_understanding": { "confirmed": [], "corrected": [], "new_insights": [] },
|
|
"new_findings": [], "new_questions": [], "timestamp": "..."
|
|
}
|
|
```
|
|
|
|
2. Append round section to `<session>/discussion.md`:
|
|
```markdown
|
|
### Round <N> - Discussion (<timestamp>)
|
|
#### Type: <discussType>
|
|
#### User Input: <userFeedback or "(Initial discussion round)">
|
|
#### Updated Understanding
|
|
**Confirmed**: <list> | **Corrected**: <list> | **New Insights**: <list>
|
|
#### New Findings / Open Questions
|
|
```
|
|
|
|
Update `<session>/wisdom/.msg/meta.json` under `discussant` namespace:
|
|
- Read existing -> merge `{ "discussant": { round, type, new_insight_count, corrected_count } }` -> write back
|