To restrict talent leakage, builders ought to present particular directions in config recordsdata in regards to the undertaking construct, take a look at operating, code conventions, and different essential context. Activity-specific directions needs to be saved in separate markdown recordsdata with descriptive names, the researchers advise.
Moreover, to keep away from conflicting directions, builders ought to periodically evaluation config recordsdata to take away directions which can be contradictory or outdated. Equally, decreasing init fossilization requires steady updating of recordsdata, the researchers defined. That is notably essential in instances the place an agent makes the identical mistake twice in a row, a code evaluation reveals a element the agent ought to have already identified, or when builders discover themselves prompting corrections and clarifications already addressed in a earlier session.
Lastly, to reduce blind references, builders ought to inform brokers when and why to learn recordsdata, and embody references with concise explanations of the doc’s function, the data it accommodates, and eventualities the place it needs to be used. As an illustration, textual content might reference an exterior dependency, embody a hyperlink to its GitHub repository, and supply a short clarification of its goal. “Then the agent is ready to perceive the function of the dependency while not having to load or examine the exterior repository immediately,” the researchers defined.
