CLID-473: subagent to generate weekly reports #116
Conversation
|
@aguidirh: This pull request references CLID-473 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: aguidirh The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-robot
added
the
needs-rebase
|
Hi @aguidirh. Thanks for your PR. I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
openshift-ci
bot
added
the
needs-ok-to-test
openshift-merge-robot
removed
the
needs-rebase
|
/ok-to-test |
openshift-ci
bot
added
ok-to-test
aguidirh
force-pushed
the
CLID-473
branch
3 times, most recently
from
f15ee3e to
502ab18
Compare
|
/jira refresh |
|
@aguidirh: This pull request references CLID-473 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Signed-off-by: Alex Guidi <[email protected]>
| @@ -0,0 +1,507 @@ | |||
| --- | |||
| name: weekly | |||
| description: Use this agent when the user requests a team activity report, sprint summary, or weekly status update. Examples:\n\n<example>\nContext: User wants to generate the weekly team activity report.\nuser: "Can you generate this week's team activity report for the CLID project?"\nassistant: "I'll use the Task tool to launch the weekly agent to generate the weekly activity report."\n<tool_use>\n<tool_name>Task</tool_name>\n<parameters>\n<task>Generate weekly team activity report for CLID project</task>\n<agent>weekly</agent>\n</parameters>\n</tool_use>\n</example>\n\n<example>\nContext: User wants a report for a specific sprint with component filtering.\nuser: "I need a report for the oc-mirror component from last week's sprint"\nassistant: "I'll launch the weekly agent to generate a filtered report for the oc-mirror component from last week."\n<tool_use>\n<tool_name>Task</tool_name>\n<parameters>\n<task>Generate team activity report for oc-mirror component with week-offset -1</task>\n<agent>weekly</agent>\n</parameters>\n</tool_use>\n</example>\n\n<example>\nContext: User wants a custom sprint report with additional notes.\nuser: "Create a sprint report for CLID Sprint 278 and include the notes from our standup meeting"\nassistant: "I'll use the weekly agent to generate a custom sprint report with your standup notes."\n<tool_use>\n<tool_name>Task</tool_name>\n<parameters>\n<task>Generate sprint report for CLID Sprint 278 including standup notes</task>\n<agent>weekly</agent>\n</parameters>\n</tool_use>\n</example> | |||
There was a problem hiding this comment.
This is probably too much content to inject into the context. I am not sure if anything after the first sentence in needed
There was a problem hiding this comment.
description: Use this agent when the user requests a team activity report, sprint summary, or weekly status update.
Everything after the sentence above are only examples, are you saying they are not needed? Is this not going to make it less accuracy ? It was basically auto-generated by claude.
| **Action**: Confirm all issues were successfully fetched and stored with COMPLETE data including changelogs and comments in individual JSON files. | ||
|
|
||
| **ABSOLUTE REQUIREMENT**: You MUST verify that all JSON files contain complete data (including changelogs and comments) before proceeding to report generation. |
There was a problem hiding this comment.
This kind of reiteration for deterministic behavior makes me think Claude had trouble with this? Turning it into a skill with a script that does exactly what you want might be more successful (and cheaper token-wise)
There was a problem hiding this comment.
Yes, I had to add it because claude was doing a lot of mistakes related to the data returned by the mcp server as json file.
Some times it was getting only part of the response and some times it was even creating fake data as part of the jira response.
There was a problem hiding this comment.
This looks more like a slash command that should be invoked rather than a subagent.
Could it also go into the jira plugin? Then we don't need duplicated steps about setting up the jira mcp server
There was a problem hiding this comment.
Currently it is already a jira plugin but as a subagent.
I decided to do that as an agent because I saw agents have their own context windows, which makes more reliable in accuracy. Also I would like to run it autonomous in some kind of weekly job.
There was a problem hiding this comment.
This is structured as its own plugin called "report-writer", the jira plugin is here https://github.com/openshift-eng/ai-helpers/tree/main/plugins/jira
For both agents and commands, the only thing in the context window is their descriptions until invoked
There was a problem hiding this comment.
Commands are more discoverable than agents, and this is definitely a command-type task to deterministically generate a weekly report.
Unless there's a compelling case/evidence this needs a dedicated context window, I would structure this more like other tools in this repo (a command, with a skill). A skill with a script to extract the JSON files you're looking for will also be much more reliable
4 participants
What this PR does / why we need it:
This PR introduces a new report-writer agent plugin that generates comprehensive weekly team activity reports by systematically collecting and analyzing data from Atlassian Jira. The agent automates the process of:
The agent follows a rigorous 5-step workflow to ensure data completeness and accuracy, with mandatory verification checkpoints and comprehensive error handling.
Which issue(s) this PR fixes:
Fixes CLID-473
Special notes for your reviewer:
Checklist: