Skip to content

Commit f8ac2fe

Browse files
authored
[WIP] Update deepreport to extract actionable agentic tasks (#6846)
1 parent 02caa63 commit f8ac2fe

2 files changed

Lines changed: 122 additions & 0 deletions

File tree

.github/workflows/deep-report.lock.yml

Lines changed: 64 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

.github/workflows/deep-report.md

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,7 @@ Continuously review and aggregate information from the various reports created a
6666
3. **Flag interesting activity** - Highlight noteworthy discoveries, improvements, or anomalies
6767
4. **Detect suspicious patterns** - Identify potential security concerns or concerning behaviors
6868
5. **Surface exciting developments** - Celebrate wins, improvements, and positive trends
69+
6. **Extract actionable tasks** - Identify exactly 3 specific, high-impact tasks that can be assigned to agents for quick wins
6970

7071
## Data Sources
7172

@@ -183,6 +184,38 @@ Connect the dots between different data sources:
183184
2. Identify agents that may be experiencing issues
184185
3. Find patterns that span multiple report types
185186
4. Track how identified patterns evolve over time
187+
5. **Identify improvement opportunities** - Look for:
188+
- Duplicate or inefficient patterns that can be consolidated
189+
- Missing configurations (caching, error handling, documentation)
190+
- High token usage in workflows that could be optimized
191+
- Repetitive manual tasks that can be automated
192+
- Issues or discussions that need attention (labeling, triage, responses)
193+
194+
### Step 3.5: Extract Actionable Agentic Tasks
195+
196+
**CRITICAL**: Based on your analysis, identify exactly **3 actionable tasks** (quick wins):
197+
198+
1. **Prioritize by impact and effort**: Look for high-impact, low-effort improvements
199+
2. **Be specific**: Tasks should be concrete with clear success criteria
200+
3. **Consider agent capabilities**: Tasks should be suitable for AI agent execution
201+
4. **Base on data**: Use insights from discussions, workflows, and issues
202+
5. **Focus on quick wins**: Tasks that can be completed quickly (< 4 hours of agent time)
203+
204+
**Common quick win categories:**
205+
- **Code/Configuration improvements**: Consolidate patterns, add missing configs, optimize settings
206+
- **Documentation gaps**: Add or update missing documentation
207+
- **Issue/Discussion triage**: Label, organize, or respond to backlog items
208+
- **Workflow optimization**: Reduce token usage, improve caching, fix inefficiencies
209+
- **Cleanup tasks**: Remove duplicates, archive stale items, organize files
210+
211+
**Output format for each task:**
212+
```
213+
Task 1: [Clear title]
214+
- Description: [What needs to be done and why]
215+
- Expected Impact: [Measurable benefit]
216+
- Suggested Agent: [Which agent can do this]
217+
- Estimated Effort: [Quick/Medium/Fast]
218+
```
186219

187220
### Step 4: Store Insights in Repo Memory
188221

@@ -243,6 +276,31 @@ Based on trend analysis, provide:
243276
- Suggestions for new agents or capabilities
244277
- Areas that need more monitoring
245278

279+
### ✅ Actionable Agentic Tasks (Quick Wins)
280+
281+
**IMPORTANT**: Extract exactly **3 actionable tasks** that could be immediately assigned to an AI agent to improve the project. Focus on **quick wins** - tasks that are:
282+
- **Specific and well-defined** - Clear scope with measurable outcome
283+
- **Achievable by an agent** - Can be automated or assisted by AI
284+
- **High impact, low effort** - Maximum benefit with minimal implementation time
285+
- **Data-driven** - Based on patterns and insights from this analysis
286+
- **Independent** - Can be completed without blocking dependencies
287+
288+
For each task, provide:
289+
1. **Task Title** - Clear, action-oriented name (e.g., "Reduce token usage in daily-news workflow")
290+
2. **Description** - 2-3 sentences explaining what needs to be done and why
291+
3. **Expected Impact** - What improvement or benefit this will deliver
292+
4. **Suggested Agent** - Which existing agent could handle this, or suggest "New Agent" if needed
293+
5. **Estimated Effort** - Quick (< 1 hour), Medium (1-4 hours), or Fast (< 30 min)
294+
295+
**If no actionable tasks are identified** (the project is in excellent shape), explicitly state: "No actionable tasks identified - the project is operating optimally."
296+
297+
**Examples of good actionable tasks:**
298+
- "Consolidate duplicate error handling patterns in 5 workflow files"
299+
- "Add missing cache configuration to 3 high-frequency workflows"
300+
- "Create automated labels for 10 unlabeled issues based on content analysis"
301+
- "Optimize token usage in verbose agent prompts (identified 4 candidates)"
302+
- "Add missing documentation for 2 frequently-used MCP tools"
303+
246304
### 📚 Source Attribution
247305

248306
List all reports and data sources analyzed:

0 commit comments

Comments
 (0)