How do I install the Openspec Spec Sync skill?

Run npx skillmds@latest add nklofy/openspec-spec-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openspec Spec Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openspec Spec Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openspec Spec Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openspec Spec Sync?

nklofy (@nklofy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openspec Spec Sync by nklofy — Agent Skill

Name: Openspec Spec Sync
Rating: 4.2 (5 reviews)
Author: nklofy

File contents

OpenSpec Spec Sync

Purpose

Apply approved change-level delta specs into canonical main specs.

This skill updates requirements documentation. It does not implement code or archive changes.

When To Invoke

Invoke when the user asks to:

sync specs
merge change specs into main specs
apply approved spec deltas
update canonical requirements after a change
prepare a change for archive after implementation

Inputs

Useful inputs include:

change name
capability name
whether to dry-run or actually update files
whether ambiguous deltas should be resolved interactively

Repository Files

This skill reads:

openspec/changes/<change-name>/specs/<capability>/spec.md

This skill creates or updates:

openspec/specs/<capability>/spec.md

Procedure

Identify the target change.
Find all change spec files under openspec/changes/<change-name>/specs/.
Locate corresponding main specs under openspec/specs/.
Parse delta sections.
Apply ADDED Requirements.
Apply MODIFIED Requirements.
Apply REMOVED Requirements.
Apply RENAMED Requirements.
Validate that main specs contain normal requirements only.
Report updated capabilities and counts.

Decision Rules

If a modified or removed requirement cannot be found, ask before inventing behavior.
If a main spec does not exist, create it only when the delta clearly defines a new capability.
If two delta operations conflict, stop and ask for resolution.
Do not leave delta headers in main specs.

Guardrails

Do not archive the change.
Do not edit code.
Do not silently drop requirements.
Do not rewrite unrelated sections of main specs.
Preserve requirement scenarios unless intentionally modified.

Output Format

Using change: <change-name>
Status: needs-spec-sync

Updated main specs:
- openspec/specs/<capability>/spec.md

Applied:
- Added: <n>
- Modified: <n>
- Removed: <n>
- Renamed: <n>

Next action: <recommended next step>

Examples

User: "Sync the auth spec from add-user-auth."

Action: apply auth delta requirements into openspec/specs/auth/spec.md and report counts.

---name: openspec-spec-syncdescription: Syncs OpenSpec delta specs into main specs. Invoke when applying approved change specs to canonical specifications.---# OpenSpec Spec Sync## PurposeApply approved change-level delta specs into canonical main specs.This skill updates requirements documentation. It does not implement code or archive changes.## When To InvokeInvoke when the user asks to:- sync specs- merge change specs into main specs- apply approved spec deltas- update canonical requirements after a change- prepare a change for archive after implementation## InputsUseful inputs include:- change name- capability name- whether to dry-run or actually update files- whether ambiguous deltas should be resolved interactively## Repository FilesThis skill reads:- `openspec/changes/<change-name>/specs/<capability>/spec.md`This skill creates or updates:- `openspec/specs/<capability>/spec.md`## Procedure1. Identify the target change.2. Find all change spec files under `openspec/changes/<change-name>/specs/`.3. Locate corresponding main specs under `openspec/specs/`.4. Parse delta sections.5. Apply `ADDED Requirements`.6. Apply `MODIFIED Requirements`.7. Apply `REMOVED Requirements`.8. Apply `RENAMED Requirements`.9. Validate that main specs contain normal requirements only.10. Report updated capabilities and counts.## Decision Rules- If a modified or removed requirement cannot be found, ask before inventing behavior.- If a main spec does not exist, create it only when the delta clearly defines a new capability.- If two delta operations conflict, stop and ask for resolution.- Do not leave delta headers in main specs.## Guardrails- Do not archive the change.- Do not edit code.- Do not silently drop requirements.- Do not rewrite unrelated sections of main specs.- Preserve requirement scenarios unless intentionally modified.## Output Format```textUsing change: <change-name>Status: needs-spec-syncUpdated main specs:- openspec/specs/<capability>/spec.mdApplied:- Added: <n>- Modified: <n>- Removed: <n>- Renamed: <n>Next action: <recommended next step>```## ExamplesUser: "Sync the auth spec from add-user-auth."Action: apply auth delta requirements into `openspec/specs/auth/spec.md` and report counts.

Frequently asked questions

Openspec Spec Sync