devflow-kit 0.6.0 → 0.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -6,7 +6,7 @@ allowed-tools: Task
6
6
 
7
7
  # Research Skill - Auto-Dispatcher
8
8
 
9
- **Purpose**: Detect when pre-implementation research is needed and auto-launch the research agent.
9
+ **Purpose**: Detect when pre-implementation research is needed and auto-launch the brainstorm agent for exploration.
10
10
 
11
11
  ## When to Activate
12
12
 
@@ -23,8 +23,8 @@ Auto-activates when:
23
23
  ```markdown
24
24
  Quick check (don't do heavy research):
25
25
  1. Is this pattern already in codebase? → Show example
26
- 2. Is this unfamiliar/complex? → Launch research agent
27
- 3. Are there multiple approaches? → Launch research agent
26
+ 2. Is this unfamiliar/complex? → Launch brainstorm agent
27
+ 3. Are there multiple approaches? → Launch brainstorm agent
28
28
  ```
29
29
 
30
30
  ## Decision Logic
@@ -34,14 +34,14 @@ Quick check (don't do heavy research):
34
34
  - Similar feature already implemented
35
35
  - Just need to reference existing code
36
36
 
37
- **Launch research agent** (unknown):
37
+ **Launch brainstorm agent** (unknown):
38
38
  - Unfamiliar feature or technology
39
39
  - New library integration
40
40
  - Multiple possible approaches
41
41
  - Need to study docs/examples
42
42
  - Integration strategy unclear
43
43
 
44
- ## Auto-Launch Research Agent
44
+ ## Auto-Launch Brainstorm Agent
45
45
 
46
46
  When research is needed:
47
47
 
@@ -49,25 +49,25 @@ When research is needed:
49
49
  I've detected this requires pre-implementation research.
50
50
 
51
51
  **Feature**: [what's being implemented]
52
- **Unknowns**: [what we need to research]
52
+ **Unknowns**: [what we need to explore]
53
53
 
54
- Launching research agent to analyze approaches and create implementation plan...
54
+ Launching brainstorm agent to explore approaches and patterns...
55
55
  ```
56
56
 
57
- Then launch the research agent using Task tool:
57
+ Then launch the brainstorm agent using Task tool:
58
58
 
59
59
  ```
60
60
  Task(
61
- subagent_type="research",
62
- description="Pre-implementation research",
63
- prompt="Conduct comprehensive research for implementing: [feature description].
61
+ subagent_type="brainstorm",
62
+ description="Explore implementation approaches",
63
+ prompt="Explore implementation approaches for: [feature description].
64
64
 
65
- Research focus:
66
- - Evaluate implementation approaches
67
- - Study official documentation and examples
68
- - Analyze existing codebase patterns
69
- - Design integration strategy
70
- - Create actionable implementation plan
65
+ Focus on:
66
+ - What approaches exist for this problem?
67
+ - What are the trade-offs of each approach?
68
+ - What patterns are already in the codebase?
69
+ - What libraries/frameworks could help?
70
+ - What are the risks and edge cases?
71
71
 
72
72
  Context: [relevant project context]"
73
73
  )
@@ -78,13 +78,15 @@ Task(
78
78
  After agent completes, summarize key findings:
79
79
 
80
80
  ```markdown
81
- 🔬 **Research Complete**
81
+ **Exploration Complete**
82
82
 
83
- **Recommended Approach**: [chosen solution]
84
- **Integration Points**: [where it fits]
85
- **Implementation Plan**: [step-by-step]
86
- **Key Considerations**: [risks/trade-offs]
87
- **Documentation**: `.docs/research/[session-id].md`
83
+ **Approaches Found**: [list of options]
84
+ **Codebase Patterns**: [relevant existing patterns]
85
+ **Recommended Direction**: [suggested approach]
86
+ **Trade-offs**: [key considerations]
87
+ **Documentation**: `.docs/brainstorm/[topic-slug]-[timestamp].md`
88
+
89
+ **Next Step**: Run `/design` to create detailed implementation plan for chosen approach.
88
90
  ```
89
91
 
90
92
  ## Examples
@@ -99,17 +101,17 @@ Skill: "We already use this pattern. See src/api/users.ts:45
99
101
  **Example 2: Unfamiliar - Launch Agent**
100
102
  ```
101
103
  User: "Add OAuth authentication"
102
- Skill: "OAuth integration requires research of approaches and patterns.
103
- Launching research agent..."
104
- [Launches research agent for comprehensive analysis]
104
+ Skill: "OAuth integration requires exploration of approaches.
105
+ Launching brainstorm agent..."
106
+ [Launches brainstorm agent for approach exploration]
105
107
  ```
106
108
 
107
109
  **Example 3: Multiple Approaches - Launch Agent**
108
110
  ```
109
111
  User: "Add real-time updates to dashboard"
110
112
  Skill: "Multiple approaches possible (WebSockets, SSE, polling).
111
- Launching research agent to evaluate options..."
112
- [Launches research agent]
113
+ Launching brainstorm agent to explore options..."
114
+ [Launches brainstorm agent]
113
115
  ```
114
116
 
115
117
  ## Quick Pattern Recognition
@@ -122,14 +124,15 @@ grep -r "similar_pattern" --include="*.ts" src/ | head -3
122
124
  ```
123
125
 
124
126
  If pattern found → Show it
125
- If not found → Launch agent
127
+ If not found → Launch brainstorm agent
126
128
 
127
129
  ## Key Points
128
130
 
129
- - **Lightweight**: Skill does minimal checking (~20 lines)
130
- - **Smart dispatch**: Shows existing patterns vs researches new
131
- - **No heavy analysis**: Delegates comprehensive research to agent
131
+ - **Lightweight**: Skill does minimal checking
132
+ - **Smart dispatch**: Shows existing patterns vs explores new options
133
+ - **Exploration focus**: Brainstorm agent explores approaches, not detailed planning
132
134
  - **Autonomous**: Auto-launches when research needed
133
135
  - **Clean context**: Main session stays focused on implementation
136
+ - **Next step guidance**: Suggests `/design` after exploration completes
134
137
 
135
- This ensures thorough research happens in separate context while main session remains clean.
138
+ This ensures thorough exploration happens in separate context while main session remains clean. For detailed implementation planning, use `/design` after exploration.