Best Practice on how to load/ingest enterprise guidance/rules to spec kit context

[TechSkieur]

Hi Folks,

I'm wondering what would be the best practice to load enterprise-level context into spec kit context when executing spec command. For big enterprise, there are many requirements on security/ethics/compliance. Also for some common modules, to build features on top of these modules, need to refer to their help guide or documents. These can be all seen as Context. It's necessary to use such Context to build new features.

So when executing spec command should we put all these context into constitution.md file, in such case, constitution.md file would become too large... or construct a multi-layer structure and load these context separately?