openspec-sync-specs SKILL.md skillA

openspec-sync-specs from cedaniel200/atlas-template is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add cedaniel200/atlas-template/openspec-sync-specs@v1.0

Pins v1.0 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

cedaniel200/atlas-template

Path

.agents/skills/openspec-sync-specs/SKILL.md

Versions recorded

1

Latest version

v1.0, committed Oct 21, 2026

Size

5,155 bytes

Repository stars

3

License

MIT

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.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

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).

**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.

**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.
…

Read the whole file at its exact version.

How to install

mdr add cedaniel200/atlas-template/openspec-sync-specs@sha256:0f8d143167bb7738

[![mdr](https://markdownregistry.com/badge/art_o3okwcknhoroxmbr.svg)](https://markdownregistry.com/a/art_o3okwcknhoroxmbr)

Versions

The registry has recorded 1 version of this file, committed on Oct 21, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_o3okwcknhoroxmbr
GET https://markdownregistry.com/api/v1/resolve?ref=cedaniel200/atlas-template/openspec-sync-specs
GET https://markdownregistry.com/api/v1/blob/0f8d143167bb7738fb8e14aaac3a7c4a0490f607f571c224fc38c407b4db94a6

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from cedaniel200/atlas-template

Every file in cedaniel200/atlas-template

Other files named openspec-sync-specs

Browse by kind, by grade A, or by owner.