mirror of
https://github.com/Fission-AI/OpenSpec.git
synced 2026-09-14 20:16:53 +08:00
d90eccf959
The update command now only updates existing AI tool configuration files instead of forcing CLAUDE.md creation. This allows team members to use different AI tools without conflicts.
1.1 KiB
1.1 KiB
Fix Update Command Tool Selection
Problem
The openspec update command currently forces the creation/update of CLAUDE.md regardless of which AI tool was selected during initialization. This violates the tool-agnostic design principle and creates confusion for users who selected different AI assistants.
Additionally, different team members may use different AI tools, so we cannot rely on a shared configuration file.
Solution
Modify the update command to:
- Only update AI tool configuration files that already exist
- Never create new AI tool configuration files
- Always update the core OpenSpec files (README.md, etc.)
Implementation
- Remove hardcoded CLAUDE.md update from update command
- Implement file existence check before updating any AI tool config
- Update each existing AI tool config file with its appropriate markers
- No configuration file needed (avoids team conflicts)
Success Criteria
- Update command only modifies existing AI tool configuration files
- No new AI tool files created during update
- Team members can use different AI tools without conflicts
- Existing projects continue to work (backward compatibility)