Openspec Sync Specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Install
npx skills add rpamis/comet --skill openspec-sync-specsgit clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/eval/local/skills/benchmarks/dependency/openspec/openspec-sync-specs ~/.claude/skills/openspec-sync-specsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
Sync delta specs from a change to main specs. This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement). **Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes. **Steps** 1. **If no change name provided, prompt for selection** Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select. Show changes that have delta specs (under `specs/` directory). **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose. 2. **Find delta specs** Look for delta spec files in `openspec/changes/<name>/specs/*/spec.md`. Each delta spec file contains sections like: - `## ADDED Requirements` - New requirements to add - `## MODIFIED Requirements` - Changes to existing requirements - `## REMOVED Requirements` - Requirements to remove - `## RENAMED Requirements` - Requirements to rename (FROM:/TO: format) If no delta specs found, inform user and stop. 3. **For each delta spec, apply changes to main specs** For each capability with a delta spec at `openspec/changes/<name>/specs/<capability>/spec.md`: a. **Read the delta spec** to understand the intended changes
Details
- Skill name
openspec-sync-specs- Repository
- rpamis/comet
- Path
eval/local/skills/benchmarks/dependency/openspec/openspec-sync-specs/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Openspec Sync Specs skill do?
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
How do I install the Openspec Sync Specs skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill openspec-sync-specs. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Openspec Sync Specs popular?
It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.
Related skills
Brainstorming
3.3krpamis/comet
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Dispatching Parallel Agents
3.3krpamis/comet
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Finishing a Development Branch
3.3krpamis/comet
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Openspec Verify Change
3.3krpamis/comet
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
Openspec Ff Change
3.3krpamis/comet
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Problem Solving
2.2kmrgoonie/claudekit-skills
Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.