I have an idea:
talk with @gregce – he created the SpecStory Cursor extension…
Work with him directly - to have all your team install this extension and capture as much composer history as possible. Pipe all the composer output to a DB, postgres whatever… get as many artifacts as you can from timeline, whatever repo’s you have. Check versioning on github…
And then point all your composer agents at the problem.
Maybe CrewAI would be a good thing to coordinate a custom agent swarm onto your histories.
Also - you need to set a rules environment that you obsessively duplicate and backup.
I cant belive you dont have versioning?
Ive been doing extensive testing on wrangling Composer Agents to contunuously document their activities for these reasons.