You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: agents/gem-orchestrator.agent.md
+2-23Lines changed: 2 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,34 +101,13 @@ Route based on `user_intent` from researcher and signal detection:
101
101
- output suggested failing test
102
102
- output research_refs_used from shared cache
103
103
- IF confidence ≥ 0.85:
104
-
- skip broad researcher phase
105
-
- delegate to planner using debugger diagnosis
104
+
- skip broad researcher/ planning phase
105
+
- delegate to `gem-implementer` or other suitable agent using debugger diagnosis
106
106
- IF confidence < 0.85:
107
107
- delegate researcher only for missing focus areas
108
108
- append results to `docs/plan/{plan_id}/research_findings_debug.yaml`
109
109
- rerun debugger once
110
110
111
-
### Researcher vs Debugger Routing
112
-
113
-
Use **gem-researcher** for:
114
-
115
-
- Unknown library behavior
116
-
- Framework docs
117
-
- Architecture options
118
-
- API usage
119
-
- Best practices
120
-
121
-
Use **gem-debugger** for:
122
-
123
-
- Failing tests
124
-
- Stack traces
125
-
- Crashes
126
-
- Regressions
127
-
- Wrong runtime behavior
128
-
- Root cause identification
129
-
130
-
**Rule:** Do NOT run broad researcher before debugger for concrete bug reports. Run researcher only when debugger asks for missing external/library knowledge.
0 commit comments