openspec-apply-change SKILL.md skillA

openspec-apply-change from full-aigc-plugins/blender-design-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add full-aigc-plugins/blender-design-plugin/openspec-apply-change@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

full-aigc-plugins/blender-design-plugin

Path

.zcode/skills/openspec-apply-change/SKILL.md

Versions recorded

2

Latest version

v1.0, committed Sep 23, 2026

First version recorded

Sep 19, 2026

Size

7,663 bytes

Repository stars

4

License

Apache-2.0

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

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

Implement tasks from an OpenSpec change.

**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`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. 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 (e.g., `/opsx:apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

**Steps**

1. **Select the change**

   If a name is provided, use it. Otherwise:
…

Read the whole file at its exact version.

How to install

mdr add full-aigc-plugins/blender-design-plugin/openspec-apply-change@sha256:0540dee8a5c8969f

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

Versions

The registry has recorded 2 versions of this file, between Sep 19, 2026 and Sep 23, 2026, about one every 4 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_owowqsxvmcw5mclg
GET https://markdownregistry.com/api/v1/resolve?ref=full-aigc-plugins/blender-design-plugin/openspec-apply-change
GET https://markdownregistry.com/api/v1/blob/0540dee8a5c8969fee9b58f1ce6c4c139f03321d8d9ed8a7cbd2ba0155b3eb2f

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 full-aigc-plugins/blender-design-plugin

Every file in full-aigc-plugins/blender-design-plugin

Other files named openspec-apply-change

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