openspec-apply-change

name	openspec-apply-change
description	Implements the pending tasks of an OpenSpec change against its proposal, specs, and design, looping until done or blocked. Use for "implement this change", "start/continue implementing", "work through the tasks", or "keep going on <change>". Can be invoked any time tasks exist, before or after other artifacts are finished, and interleaved with artifact updates — it is not phase-locked to a single point in the change's lifecycle.
compatibility	Requires the openspec CLI on PATH.

Implement OpenSpec change tasks

Work through a change's task checklist against real code, one task at a time, checking each off only once it is actually done.

Steps

1. Select the change. Use a given name; otherwise infer from context, or auto-select if only one active change exists. If ambiguous, run openspec list --json and let the user choose. Always announce which change is in use.

2. Check status: openspec status --change "<name>" --json — read schemaName and which artifact holds the tasks.

3. Get apply instructions:

   openspec instructions apply --change "<name>" --json
   

   Returns contextFiles (artifact ID -> file paths), task progress, the task list with status, and a dynamic instruction. If state: "blocked" (missing artifacts), suggest /openspec-continue-change. If state: "all_done", congratulate and suggest /openspec-archive-change.