⇩ Markdown

agent task -- change review app

agent task -- change review app


When an agent task makes some substantive change after being triggered then it may need to ultimately be reviewed by a person.

Since the big problem is bottleneck - human reviewers, you want to make dim - review ease -- higher. You should think of this "review app" as everything needed to make it super easy for the person to approve or provide feedback.

Why an app? Because of the level of interactivity that the reviewer would benefit from.  And it's a pro tool, so could be mostly keyboard driven, even.

This app is the representation of the change. breakthrough that comes from a better representation

How do people see this review app?

I'm being a little vague here, since I'm a solo-developer at this point and don't use PRs, but in a traditional setup these reviews could be associated with pull request - PR

What does the app contain?

A text-based description of the changes

For changes with UI, a video showing UI before and after and also the full gallery of the other feature videos for comparison. Perhaps each test scenario has time travelable application state data

A development environment playground where the user can play with the thing, look at the code if they want to, and even make tweaks to try something different (which in-turn creates another review packet, ultimate). A User Acceptance Test - UAT that walks them through what to test

Maybe the agent thread, so they can see the reasoning behind it

documentation context graph -- document (basically the original spec that motivated the change) with the change areas highlighted. Perhaps like tweet - coginitive debt reduction visualization

cognitive debt reduction artifacts like an architectural change walkthrough (architectural visualization) or even, perhaps, spaced repetition prompts that the person could decide to pull into their retrieval practice.

Speculative merge (and rebase) results. If the tests had been run on master right now, would they pass? (On reason why fast CI is a good idea)


Loosely referred to as proof of work in Symphony