openspec-apply-change is agent-read markdown (skill) from muthuishere/toolnexus: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
Implement tasks from an OpenSpec change.
**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. **Select the change**
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists
- If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
2. **Check status to understand the schema**
```bash
openspec status --change "<name>" --json
```
Parse the JSON to understand:
- `schemaName`: The workflow being used (e.g., "spec-driven")
- `planningHome`, `changeRoot`, and `actionContext`: planning scope and edit constraints
- Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
3. **Get apply instructions**
```bash
openspec instructions apply --change "<name>" --json
```
This returns:
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_4q7x4zqvcwu7o7nj
GET https://markdownregistry.com/api/v1/resolve?ref=muthuishere/toolnexus/openspec-apply-change
GET https://markdownregistry.com/api/v1/blob/da3d97f3ea482cca969981a2079ce7f906ccb4a892728f07bf72f354035d951a
Your agent 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.
muthuishere/toolnexus · .claude/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
muthuishere/toolnexus · .claude/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
muthuishere/toolnexus · .claude/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
muthuishere/toolnexus · .claude/skills/openspec-sync-specs/SKILL.md · Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta…
muthuishere/toolnexus · .claude/skills/release/SKILL.md · Cut and verify a toolnexus release across all seven registries, with the guardrails that a green CI run does not give…
muthuishere/toolnexus · clojure/examples/clj-ex1/skills/clojure-events/SKILL.md · Use when asked about Clojure community events, meetups or conferences. How to fetch and report them.
muthuishere/toolnexus · clojure/examples/cljgo-ex1/skills/clojure-events/SKILL.md · Use when asked about Clojure community events, meetups or conferences. How to fetch and report them.
muthuishere/toolnexus · examples/skills/hello-world/SKILL.md · A tiny example skill. Use when you want to see how skill loading (progressive disclosure) works end to end.
partcad/partcad · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
partcad/partcad · .cursor/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
monid-ai/monid · .opencode/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
intent-driven-dev/intent-driven-template · .opencode/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
rustyrazorblade/skills · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
yazelin/ching-tech-os · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
yazelin/ching-tech-os · .github/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
jim60105/copilot-prompt · skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
