Spec-Kit + Codex Re-init Problem After Merging to main #1275
Description
Summary
After merging a feature PR into main, the project behaves as if it is not a Spec-Kit project anymore.
Spec-Kit asks to run specify init again, which overwrites constitution.md back to the vanilla template.
Expected
• Spec-Kit should recognize the project on all branches.
• No re-initialization should be required after merges.
• Governance files (e.g., constitution.md) must never be reset unless explicitly requested.
Actual
• On main after a merge, Spec-Kit warns:
• “Project does not seem to be a Spec-Kit project”
• “Template files may overwrite existing content”
• Running init resets important files.
Likely Cause
• Spec-Kit project markers (e.g., hidden metadata files) may not be committed or are lost during merges.
• Codex metadata may remain local and not sync with the repo.
Questions for Maintainers
1. Which files define that a repo is a Spec-Kit project?
2. Which of them must be committed?
3. How to prevent constitution.md from being overwritten during normal iteration?
Request
Need guidance on the correct workflow to preserve Spec-Kit initialization across multiple features without losing governance documents.