OpenSpec Sync Specs
Use this skill when the user wants to update openspec/specs/ before archiving.
Workflow
-
Resolve the target change.
-
Find delta specs under:
openspec/changes/<name>/specs/*/spec.md
-
For each delta spec:
- read the delta spec
- read the corresponding main spec under
openspec/specs/<capability>/spec.md - merge changes intelligently instead of copying wholesale
-
Handle sections intentionally:
ADDED Requirements: add missing requirementsMODIFIED Requirements: patch only the changed portions and preserve untouched scenariosREMOVED Requirements: remove the requirement blockRENAMED Requirements: rename in place
-
If the main spec does not exist:
- create it with a short purpose section
- add the new requirements from the delta
-
Summarize which capabilities changed and how.
Notes
- This skill is mainly for cases where the user wants specs synced before archive.
- If the user is ready to close the change,
openspec-archive-changeis usually the better path. - In the repo delivery flow, sync specs before PR creation/merge when the change remains active; otherwise archive before PR creation/merge.
- Use OpenSpec CLI with telemetry disabled by default:
OPENSPEC_TELEMETRY=0 openspec ...
Guardrails
- Preserve existing content not mentioned by the delta.
- Keep the merge idempotent.
- Ask before making destructive removals when the delta is ambiguous.