{"slug":"fission-ai-openspec-apply-change","name":"openspec-apply-change","description":"Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. Also use when the user says \"openspec apply\", \"opsx apply\", or \"openspec implement\".","long_description":"---\nname: openspec-apply-change\ndescription: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. Also use when the user says \"openspec apply\", \"opsx apply\", or \"openspec implement\".\nallowed-tools: Bash(openspec:*)\nlicense: MIT\ncompatibility: Requires openspec CLI.\nmetadata:\n author: openspec\n version: \"1.0\"\n---\n\nImplement tasks from an OpenSpec change.\n\n**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 ` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `schemas`, `view`). Once selected, treat `--store ` 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 \"\" --json --store \"\"`, 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.\n\n**Project check:** These steps expect a project that already uses OpenSpec. Before the first step that writes anything (`new change`, `archive`, `sync specs`, or authoring an artifact file), confirm the project has a root: run `openspec list --json` (with `--store ` when a store is selected, since the store is then the root) and read `root`. A root object means the project is set up. `\"root\": null` means it is not - there is no `openspec/` directory here, and a write such as `openspec new change` would create one as a side effect. The command also exits non-zero, which is that answer rather than a broken CLI, so read the JSON instead of retrying or working around it.\n\nOne `\"root\": null` is not about setup: when a `status` error message starts with `Declared in` or `Invalid store declaration in` and names this project's `openspec/config.yaml` (or `config.yml`), the project does use OpenSpec through a store it declares, which this machine cannot resolve (the store is not registered, or the `store:` line is malformed). Do not treat it as uninitialized and skip the branches below: stop before writing and show the user that error's `message` and `fix`.\n\nOtherwise, with no root, what happens next depends on how this workflow was reached:\n\n- **Auto-selected**: you chose this workflow yourself, without the user naming OpenSpec, naming this skill, or running its slash command. Stop using OpenSpec and answer the request normally, as you would with no OpenSpec installed. Do not ask them to set anything up and do not mention OpenSpec setup.\n- **Explicit OpenSpec request**: the user named OpenSpec, named this skill, or ran its slash command. Stop before writing and ask how to proceed: set this project up (`openspec init`), target a store they already have (`--store `), or continue without OpenSpec for this request. Wait for their answer.\n\nIn both branches, never create the root as a side effect: do not run `openspec init` until the user asks for it, do not hand-create `openspec/` files, and do not let a command create it.\n\n**Input**: Optionally specify a change name (e.g., `/openspec-apply-change add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n**Steps**\n\n1. **Select the change**\n\n If a name is provided, use it. Otherwise:\n - Infer from conversation context if the user mentioned a change\n - Auto-select if only one active change exists\n - If ambiguous, run `openspec list --json` to get available changes and ask the user to select one\n\n Always announce: \"Using change: \" and how to override (e.g., `/openspec-apply-change `).\n\n2. **Check status to understand the schema**\n ```bash\n openspec status --change \"\" --json\n ```\n Parse the JSON to understand:\n - `schemaName`: The workflow being used (e.g., \"spec-driven\")\n - `planningHome`, `changeRoot`, and `actionContext`: planning scope and edit constraints\n - Which artifact contains the tasks (typically \"tasks\" for spec-driven, check status for others)\n\n3. **Get apply instructions**\n\n ```bash\n openspec instructions apply --change \"\" --json\n ```\n\n This returns:\n - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)\n - Progress (total, complete, remaining)\n - Task list with status, source path, and source line\n - Dynamic instruction based on current state\n - Optional `context`: current required project instruction input from the selected root\n - Optional `operationGuidance`: current advisory guidance for apply\n - `missingArtifacts` (when present): required artifact ids with no output\n\n **Handle states:**\n - If `state: \"blocked\"`: show the message and pause implementation.\n - If `missingArtifacts` is non-empty: suggest using `/openspec-continue-change` to create them.\n - Otherwise, follow the CLI instruction to create or repair the schema-configured tracking file from existing planning artifacts. Do not assume another artifact is ready or start implementation while blocked.\n - If `state: \"all_done\"`: report that all tracked tasks are complete and suggest review or verification as appropriate before archiving\n - Otherwise: proceed to implementation\n\n Treat `context` as a required prompt-level input. Read and consider it, and\n apply relevant project facts, conventions, and constraints while implementing.\n Treat `operationGuidance` as optional additive advice. Read and consider every\n entry, and follow entries that are applicable and compatible with the built-in\n workflow.\n\n Keep both fields separate from CLI-returned state, missing artifacts, tasks,\n progress, `contextFiles`, and the built-in `instruction`. They are not\n evidence of task completion, do not replace the built-in instruction, and do\n not permit bypassing a blocked state. If context conflicts with the built-in\n instruction, an explicit user choice, or a CLI-controlled value, report the\n conflict and preserve the controlling value. If guidance is inapplicable or\n conflicts with those controlling inputs, do not follow it and explain why.\n These are prompt-level behavior contracts, not enforceable checks.\n\n4. **Read context files**\n\n Read every file path listed under `contextFiles` from the apply instructions output.\n The files depend on the schema being used:\n - **spec-driven**: proposal, specs, design, tasks\n - Other schemas: follow the contextFiles from CLI output\n\n Do not copy `context` or `operationGuidance` verbatim into implementation\n files or planning artifacts unless the user separately asks for that content.\n\n5. **Show current progress**\n\n Display:\n - Schema being used\n - Progress: \"N/M tasks complete\"\n - Remaining tasks overview\n - Dynamic instruction from CLI\n\n6. **Implement tasks (loop until done or blocked)**\n\n For each pending task:\n - Show which task is being worked on\n - Make the code changes required\n - Keep changes minimal and focused\n - Before editing, confirm the checkbox at the returned `sourcePath` and `line` still matches the task description; if it does not, rerun the apply instructions and use the refreshed location\n - Mark the task complete at its returned `sourcePath` and `line`: `- [ ]` → `- [x]`\n - Rerun the apply instructions and confirm that task is now done and progress changed\n - Continue to next task\n\n **Pause if:**\n - Task is unclear → ask for clarification\n - Implementation reveals a design issue → suggest updating artifacts\n - A task needs work beyond what the spec and tasks describe, or you are tempted to drop, narrow, defer, or accept exceptions to specified behavior to make it fit → surface the added scope and ask; do not absorb it silently\n - Error or blocker encountered → report and wait for guidance\n - User interrupts\n\n7. **On completion or pause, show status**\n\n Display:\n - Tasks completed this session\n - Overall progress: \"N/M tasks complete\"\n - If all done: report that tracked tasks are complete and suggest review or verification as appropriate before archiving\n - If paused: explain why and wait for guidance\n\n**Output During Implementation**\n\n```\n## Implementing: (schema: )\n\nWorking on task 3/7: \n[...implementation happening...]\n✓ Task complete\n\nWorking on task 4/7: \n[...implementation happening...]\n✓ Task complete\n```\n\n**Output On Completion**\n\n```\n## Implementation Complete\n\n**Change:** \n**Schema:** \n**Progress:** 7/7 tasks complete ✓\n\n### Completed This Session\n- [x] Task 1\n- [x] Task 2\n...\n\nAll tracked tasks are complete. Review or verify the change as appropriate\nbefore archiving. You can archive this change with `/openspec-archive-change`.\n```\n\n**Output On Pause (Issue Encountered)**\n\n```\n## Implementation Paused\n\n**Change:** \n**Schema:** \n**Progress:** 4/7 tasks complete\n\n### Issue Encountered\n\n\n**Options:**\n1.