馃搶 Current Status
Currently, Spec-kit creates multiple folders at the root of the project:
-
scripts and templates for its own source
-
memory and specs for the project being developed
-
Additional folders like .github, depending on the IDE
This results in a cluttered root directory where Spec-kit files appear alongside core product source files.
馃挕 Proposal
To reduce root-level clutter and improve organization, consolidate all Spec-kit-related files into a dedicated dot folder for all the speck-kit stuff. Choose for one of the above:
馃 Additionally, consider storing memory and specs in the standard docs/ folder, as they pertain to project documentation.
馃攣 Alternative
Alternatively, align with existing IDE or agent conventions. For example:
- Use the
.github folder when integrating with GitHub Copilot for storing templates as instructions. (See AIDDbot example)
馃搶 Current Status
Currently, Spec-kit creates multiple folders at the root of the project:
scriptsandtemplatesfor its own sourcememoryandspecsfor the project being developedAdditional folders like
.github, depending on the IDEThis results in a cluttered root directory where Spec-kit files appear alongside core product source files.
馃挕 Proposal
To reduce root-level clutter and improve organization, consolidate all Spec-kit-related files into a dedicated dot folder for all the speck-kit stuff. Choose for one of the above:
.ai.spec-kit馃攣 Alternative
Alternatively, align with existing IDE or agent conventions. For example:
.githubfolder when integrating with GitHub Copilot for storing templates as instructions. (See AIDDbot example)