breaking upgradeability by altering the templates

[foertel]

hey,

it's maybe not good practice to let /constitution alter the templates directly. This will go "bye, bye 👋" if I tried to upgrade spec-kit.

maybe we should split the templates up into a static part in /templates and a modifiable part in /memory and then merge them at execution. 🤔

[albahrani]

This is most likely related to the upgrade discussion. It would be grate tohave your thoughts there.

[foertel]

Maybe we should write modified templates to .specify/memory/templates and when updating, ask the user - apt-like - if they want to keep using their own or use the maintainers new version.

Then we would just have to check if a memory template exists here (and here for ps) and otherwise use the template one.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 150 days. It will be closed in 30 days if no further activity occurs.

[github-actions]

This issue has been automatically closed due to inactivity (180 days total). If you believe this issue is still relevant, please reopen it or create a new issue.