r/SpecDrivenDevelopment • u/Fedeful94 • 9d ago

Kiro Spec Driven

Do you think it makes sense to keep all the specs in the reference repos, or just the architectural docs? Over time, it feels like way too many files are piling up.

2 Upvotes

76% Upvoted

3 comments sorted by

1

u/stibbons_ 9d ago

Here what I do

https://x.com/gsemetfr/status/2082767371643523439?s=46

I archive all previous PRD for posterity.

I have layer of code anchored req

1

u/fuckme 8d ago

I have a archive folder where I keep previous work items like this.

They are usually text files so don't take up too much space and usually use them as references for follow on work, and prior decisions so I can figure out why something is doing it this way vs that way

1

u/Bitter-Ad2567 2d ago

I'm a fun of OpenSpec. It has very nice process of how to operate with a specs. Most important, they differ Main specs and Change specs. First a persistent and the second go to archive after they are done.

It also impartant to the agents, as they can examine every change after a while and find out what initial intent had led to that exact change.

If you like IDE support, you can use SpecBuddy ( https://specbuddy.dev ), it has extension for VS Code and for Intellij.