-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Description
I'm trying to use spec-kit to rewrite my trading platform, which was built in last 5 month from 0 to 1. The platform have modules on different layers, from infrastructure, business processors to open API exposed.
I would like to understand how should I organize my project/code with spec-kit? Should I treat it as a huge but single project with all sub modules together and share the same copy of spec/plan/task.md? Or should I break the project down to several sub modules and focus on its area with its own spec/plan/task.md only?
If it's former, it may mean that I will have a huge spec/plan/task and any changes in single point would cause the rebuilding against the whole project, and costs lots of tokens.
But if I choose the latter, how should I combine these sub modules together? In a maven project, there is a center repository to manage all potential dependencies, and what I need to do is just clarify a reference in pom. But in spec-kit, how to clarify a reference to the dependency on these sub modules? Especially for those sub module's spec/plan/task.md file, because without them, the integration part have no idea about the purpose of given module and how to use it.