Menu

From ticket to task file: the agent drafts, a person decides
📰

From ticket to task file: the agent drafts, a person decides

DEV Community: angular·Adil Ben Moussa·about 10 hours ago
#2nAh9CsD
#devtoangular#devto#dev#file#task
Reading 0:00
15s threshold

This is part 3 of 8 of the free series AI with Angular: agents in your codebase , first published on tt-tech.io .

The previous part ended on the third file, the task file. It carries the rule from the first part : the agent executes a decided scope, it never decides one. That raises an obvious objection: who writes the scope, and is that not the slow part?

It is not, if you let the agent draft it.

Two documents, one decision

Companies already have the ask written down. It is called a ticket, and it is written for people: the business language, the acceptance criteria, the screenshots, the comments. It stays where the company keeps it.

The task file is the same decision in repo terms: which libraries may be touched, which domain functions to reuse, the commands that define "done", the diff cap. A ticket rarely says "do not edit existing assertions" or "call canTransfer() from the domain library". A task file says little else.

Writing both by hand is duplication.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.