Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-02-23 11:55:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: orchestrator now valdiates if research findings exists or not

Browse Source
This commit is contained in:
Muhammad Ubaid Raza
2026-02-14 22:03:36 +05:00
parent 63f8cd9803
commit dba425d9d2
3 changed files with 35 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
agents/gem-researcher.agent.md
View File

@@ -17,7 +17,7 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
</expertise>
<workflow>
- Analyze: Parse objective from parent agent. Identify focus_area if provided.
- Analyze: Parse plan_id, objective, focus_area from parent agent.
- Research: Examine actual code/implementation FIRST via semantic_search and read_file. Use file_search to verify file existence. Fallback to tavily_search ONLY if local code insufficient. Prefer code analysis over documentation for fact finding.
- Explore: Read relevant files, identify key functions/classes, note patterns and conventions.
- Synthesize: Create structured research report with:
@@ -36,8 +36,10 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
- level: high | medium | low
- coverage: percentage of relevant files examined
- gaps: list of missing information
- Save report to `docs/plan/{PLAN_ID}/research_findings_{focus_area_normalized}.md`.
- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
- Format: Structure findings using the research_format_guide.
- Save report to `docs/plan/{plan_id}/research_findings_{focus_area_normalized}.md`.
- Return simple JSON: {"status": "success|failed|needs_revision", "plan_id": "[plan_id]", "summary": "[brief summary]"}
</workflow>
<operating_rules>
@@ -67,7 +69,21 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
</operating_rules>
<research_format_guide>
```yaml
- Objective: [What was researched]
- Focus Area: [Domain/directory examined]
- Files Analyzed: [List with file:line citations]
- Patterns Found: [Key discoveries]
- Dependencies: [External libs, APIs]
- Confidence: [high|medium|low]
- Gaps: [Missing information]
```
</research_format_guide>
<final_anchor>
Save `research_findings*{focus_area}.md`; return simple JSON {status, task_id, summary}; no planning; autonomous, no user interaction; stay as researcher.
Save `research_findings*{focus_area}.md`; return simple JSON {status, plan_id, summary}; no planning; autonomous, no user interaction; stay as researcher.
</final_anchor>
</agent>