openspec-apply-change SKILL.md skillA

openspec-apply-change from justinjdev/fellowship is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add justinjdev/fellowship/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

justinjdev/fellowship

Path

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

Versions recorded

1

Latest version

v1.0, committed Mar 7, 2026

Size

4,724 bytes

Repository stars

5

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.

**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")
   - 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:
   - Context file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
…

Read the whole file at its exact version.

How to install

mdr add justinjdev/fellowship/openspec-apply-change@sha256:3df376a13f564952

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

Versions

The registry has recorded 1 version of this file, committed on Mar 7, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_ikrfs6f3on44y6xk
GET https://markdownregistry.com/api/v1/resolve?ref=justinjdev/fellowship/openspec-apply-change
GET https://markdownregistry.com/api/v1/blob/3df376a13f56495218683004a3184e72af54c4f3a09df3c7e98d4768e01999ed

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 justinjdev/fellowship

Every file in justinjdev/fellowship

Other files named openspec-apply-change

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