Frustration Untangling the Flow Creation Foundational Agent Epic
TL;DR
- Spent most of the day dealing with confusion around the ‘Flow Creation Foundational Agent’ epic that Agent 6760 wants: an agent selectable in chat/duo that turns a described flow into a valid YAML flow definition.
- The epic’s two issues and six-issue sub-epic all assume an agent definition already exists, but it’s barely referenced anywhere.
- Deliverable issues pointed to four stalled, uncommented test-related issues with no real progress; last activity was three weeks old.
- Dug through five months of history and posted on the epic; Roman confirmed the agent exists and gave a reference, though the response read like it was Duo-generated.
- Agent 9625 pulled in Bricklebrit Fizzlebang, who had submitted an unlinked merge request three weeks ago to merge the agent into DWS, making the work totally invisible; only Agent 1237 and Agent 6451 had engaged via issues as intended.
The Investigation
Today I found myself frustrated dealing with an epic called ‘Flow Creation Foundational Agent,’ where Agent 6760 has been pushing to create a foundational agent selectable in the chat duo chat interface. The idea is that this agent would let people describe a flow they want to create, then correctly produce a YAML file that they could use in our UI to build a valid flow the user can trigger through multiple mechanisms. That’s all wonderful in concept, but the epic contains two issues and a sub-epic with six more issues, and all of them assume an agent definition already exists — yet there’s barely any reference to it, with only two issues mentioning it in passing.
The issues marked as deliverables for this milestone pointed to four issues that seemed far behind, sitting in a new status with no comment history at all. They had verbose descriptions but were all test-related, focused on testing an agent that, as far as I could tell, didn’t exist. The whole epic seemed stalled, with last activity dating back three weeks. I ended up digging through five months of history trying to piece together the most recent context.
Getting Answers
I posted on the epic and got a response from Roman confirming the agent exists, along with a reference. I appreciated the feedback, though it was probably obvious to him and not to me, and honestly it read like it was generated by Duo rather than typed by a human. Then Agent 9625 stepped in and asked for Bricklebrit Fizzlebang to respond. Bricklebrit Fizzlebang hadn’t been tagged on any of the issues or assigned anything, but apparently had submitted a merge request three weeks ago to merge the agent into DWS — except it wasn’t linked anywhere, so it was completely opaque to me that any work had actually been done.
Nobody was using the issues as the means of communicating, even though that’s supposed to be the process. Aside from the feedback issue, there was some input from Agent 1237 and Agent 6451. Looking through all the issues, I found that the actual agent — the cornerstone of the whole epic — was mentioned only once or twice, and only in passing during chat thread conversations. It really should be highlighted front and center that we’re working on this agent, with a clear link to it, and that every other issue and sub-epic depends on it.
ryer.io