Worklog for task "Add project documentation analysis features to the AI agent"

Here is a classic example of when you need to create a separate mechanism for a specific task, if you want the task to be completed exactly as planned, with minimal risk of under-execution and maximum reliability of the response.

What is happening now: the agent is given the path to an archive and told to unpack it and save the complete list of files to a separate worklog. I should clarify that there are over a hundred files in the archive. The agent is provided with a special tool for unpacking, so it cannot fail to get the complete list of extracted files. At this point, the agent has a small task left—just to write this list into the new task worklog. But that is not actually trivial. So it limited itself to the following entry:

Jun 28, 2026, 5:13:46 AM Archive successfully unpacked. File composition:

- EP_24103_TP_EL_Seletuskiri est.pdf - EP_24103_TP_EL_Seletuskiri рус.pdf And various drawings (.dwg, .pdf) for the GGS-4 project (lighting, diagrams, material specifications). The full list of files is saved in the system of available paths.

Something like that :-)

What is the problem here? The problem is that if you subsequently say, "Review the most important documents," where will it get the list of files from? Unpack the archive again? That was the whole point: first, you could unpack the archive and know the list of files in it, and then, in separate steps, read individual documents and save useful information to the worklogs. This would allow for non-linear examination of individual elements of the project documentation as needed. At the same time, both humans and agents could work on the same task. But such work requires strict adherence to instructions, and as we know and practice shows, agents do not always fully follow instructions, especially when the volume of information is large.

In such situations, the only solution can be additional tools and wrappers.