For those who are following along with the evolution of my Blog Writing application: after the last revision (allowing follow-up questions to a query) Copilot evaluated my Pull Request and sent me an email that the follow-up was not, in fact, being added to the research stage. This was because the original research was in place and so that step was skipped.
Copilot and I fixed this with the following changes:
Refined follow-ups now reset stale state so the workflow re-enters research instead of reusing old draft/research data.
Updated in ResearchState.cs:80-105
This clears the draft, research findings, review notes, and revision state before the next run.
The blogger routing now correctly sees “no research” after a refinement and sends the next step back to the researcher.
The logic is in BloggerAgent.cs:24-68
The behavior is covered by BloggerAgentRoutingTests.cs:34-58
The researcher’s console output now prints the full query, including the original task and the follow-up refinement, rather than just the bare subtask label.
Updated in ResearcherAgent.cs:69-84
We also added regression tests for both the reset behavior and the routing behavior:
This cycle of using Copilot to generate code and tests, reviewing that code, posting a PR to GitHub, getting back feedback from Copilot and, as needed, making revisions and creating another PR is a powerful development cycle.
For more on this see Copilot Code Review
Note: The initial draft of this post was written by BlogWriter and then edited by Jesse Liberty
Illustrations by Copilot. Caution: LLMs make mistakes; this post is offered as is.
