I have been beavering away and have generated about 15-20 specs that are related to a single initial project which spawned a ton of bug fixes and incremental improvements. My question is, would it be worthwhile to ask consolidate all those into a single spec for future reference? I hesitate because that might be quite expensive and I don't even know if Kiro can do it in a day.
#Is it worthwhile to ask Kiro to consolidate 15-20 past specs into one?
strong oar
green tendon
What value are you looking to get by consolidating them? I view specs almost as change logs. Since a lot of the work is documented, you can easily track not only what commit but what spec that change came from. If you're looking to cleanup a repo maybe, then I'd just add a .gitignore for the specs (though I have had kiro recognize wrk done in a previous spec so I find value in having them included)
strong oar
- They are long, disorganized, and hard to scan.
- I want a single accurate state-of-the-repo design document.
strong oar
Occurred to me that I can ask a free LLM interface to summarize these docs for me. So my next question for Kiro team is whether there is any advantage to me in having Kiro do it rather than some other tool?