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, schemas, 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.
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 <id> 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.
One "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.
Otherwise, with no root, what happens next depends on how this workflow was reached:
- 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.
- 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 <id>), or continue without OpenSpec for this request. Wait for their answer.
In 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.
Input: Optionally specify a change name (e.g., $openspec-apply-change (Codex) or /openspec-apply-change (other agents) add-auth). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
Steps
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 ask the user to select one
Always announce: "Using change: " and how to override (e.g., $openspec-apply-change (Codex) or /openspec-apply-change (other agents) <other>).
Check status to understand the schema
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)
Get apply instructions
openspec instructions apply --change "<name>" --json
This returns:
contextFiles: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
- Progress (total, complete, remaining)
- Task list with status
- Dynamic instruction based on current state
- Optional
context: current required project instruction input from the selected root
- Optional
operationGuidance: current advisory guidance for apply
missingArtifacts (when present): required artifact ids with no output
Handle states:
- If
state: "blocked": show the message and pause implementation.
- If
missingArtifacts is non-empty: suggest completing the missing artifacts. Run openspec status --change "<name>" --json, select the next ready artifact (not skipped or blocked), and use openspec instructions "<artifact-id>" --change "<name>" --json for its rules and template. Keep the selected --store <id> on both commands.
- 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.
- If
state: "all_done": congratulate, suggest archive
- Otherwise: proceed to implementation
Treat context as a required prompt-level input. Read and consider it, and
apply relevant project facts, conventions, and constraints while implementing.
Treat operationGuidance as optional additive advice. Read and consider every
entry, and follow entries that are applicable and compatible with the built-in
workflow.
Keep both fields separate from CLI-returned state, missing artifacts, tasks,
progress, contextFiles, and the built-in instruction. They are not
evidence of task completion, do not replace the built-in instruction, and do
not permit bypassing a blocked state. If context conflicts with the built-in
instruction, an explicit user choice, or a CLI-controlled value, report the
conflict and preserve the controlling value. If guidance is inapplicable or
conflicts with those controlling inputs, do not follow it and explain why.
These are prompt-level behavior contracts, not enforceable checks.
Read context files
Read every file path listed under contextFiles from the apply instructions output.
The files depend on the schema being used:
- spec-driven: proposal, specs, design, tasks
- Other schemas: follow the contextFiles from CLI output
Do not copy context or operationGuidance verbatim into implementation
files or planning artifacts unless the user separately asks for that content.
Show current progress
Display:
- Schema being used
- Progress: "N/M tasks complete"
- Remaining tasks overview
- Dynamic instruction from CLI
Implement tasks (loop until done or blocked)
For each pending task:
- Show which task is being worked on
- Make the code changes required
- Keep changes minimal and focused
- Mark task complete in the tasks file:
- [ ] → - [x]
- Continue to next task
Pause if:
- Task is unclear → ask for clarification
- Implementation reveals a design issue → suggest updating artifacts
- 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
- Error or blocker encountered → report and wait for guidance
- User interrupts
On completion or pause, show status
Display:
- Tasks completed this session
- Overall progress: "N/M tasks complete"
- If all done: suggest archive
- If paused: explain why and wait for guidance
Output During Implementation
## Implementing: <change-name> (schema: <schema-name>)
Working on task 3/7: <task description>
[...implementation happening...]
✓ Task complete
Working on task 4/7: <task description>
[...implementation happening...]
✓ Task complete
Output On Completion
## Implementation Complete
**Change:** <change-name>
**Schema:** <schema-name>
**Progress:** 7/7 tasks complete ✓
### Completed This Session
- [x] Task 1
- [x] Task 2
...
All tasks complete! You can archive this change with `$openspec-archive-change (Codex) or /openspec-archive-change (other agents)`.
Output On Pause (Issue Encountered)
## Implementation Paused
**Change:** <change-name>
**Schema:** <schema-name>
**Progress:** 4/7 tasks complete
### Issue Encountered
<description of the issue>
**Options:**
1. <option 1>
2. <option 2>
3. Other approach
What would you like to do?
Guardrails
- Keep going through tasks until done or blocked
- Always read context files before starting (from the apply instructions output)
- If task is ambiguous, pause and ask before implementing
- If implementation reveals issues, pause and suggest artifact updates
- Keep code changes minimal and scoped to each task
- Update task checkbox immediately after completing each task
- Pause on errors, blockers, or unclear requirements - don't guess
- When a task needs work beyond what the spec describes, surface the added scope and pause - never silently narrow, defer, or simplify away specified behavior
- Only mark a task
- [x] when its specified behavior is fully implemented, not when it is partially done or deferred
- Use contextFiles from CLI output, don't assume specific file names
- Do not use context or operation guidance as proof that a task is complete
- Apply relevant project context; report conflicts with controlling workflow inputs
- Consider every guidance entry; explain any inapplicable or conflicting advice
- Do not copy runtime context or operation guidance into implementation files or planning artifacts
- Preserve CLI-controlled blocked/ready/all-done behavior and completion criteria
Fluid Workflow Integration
This skill supports the "actions on a change" model:
- Can be invoked anytime: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
- Allows artifact updates: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
1---2name: openspec-apply-change3description: 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".4allowed-tools: Bash(openspec:*)5license: MIT6compatibility: Requires openspec CLI.7metadata:8 source: https://skillmd.com/skills/vs4vijay/openspec-apply-change9 author: openspec10 version: "1.0"11 generatedBy: "1.13.1"12---1314Implement tasks from an OpenSpec change.1516**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`, `schemas`, `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.1718**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 <id>` 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.1920One `"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`.2122Otherwise, with no root, what happens next depends on how this workflow was reached:2324- **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.25- **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 <id>`), or continue without OpenSpec for this request. Wait for their answer.2627In 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.2829**Input**: Optionally specify a change name (e.g., `$openspec-apply-change (Codex) or /openspec-apply-change (other agents) add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.3031**Steps**32331. **Select the change**3435 If a name is provided, use it. Otherwise:36 - Infer from conversation context if the user mentioned a change37 - Auto-select if only one active change exists38 - If ambiguous, run `openspec list --json` to get available changes and ask the user to select one3940 Always announce: "Using change: <name>" and how to override (e.g., `$openspec-apply-change (Codex) or /openspec-apply-change (other agents) <other>`).41422. **Check status to understand the schema**43 ```bash44 openspec status --change "<name>" --json45 ```46 Parse the JSON to understand:47 - `schemaName`: The workflow being used (e.g., "spec-driven")48 - `planningHome`, `changeRoot`, and `actionContext`: planning scope and edit constraints49 - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)50513. **Get apply instructions**5253 ```bash54 openspec instructions apply --change "<name>" --json55 ```5657 This returns:58 - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)59 - Progress (total, complete, remaining)60 - Task list with status61 - Dynamic instruction based on current state62 - Optional `context`: current required project instruction input from the selected root63 - Optional `operationGuidance`: current advisory guidance for apply64 - `missingArtifacts` (when present): required artifact ids with no output6566 **Handle states:**67 - If `state: "blocked"`: show the message and pause implementation.68 - If `missingArtifacts` is non-empty: suggest completing the missing artifacts. Run `openspec status --change "<name>" --json`, select the next `ready` artifact (not `skipped` or `blocked`), and use `openspec instructions "<artifact-id>" --change "<name>" --json` for its rules and template. Keep the selected `--store <id>` on both commands.69 - 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.70 - If `state: "all_done"`: congratulate, suggest archive71 - Otherwise: proceed to implementation7273 Treat `context` as a required prompt-level input. Read and consider it, and74 apply relevant project facts, conventions, and constraints while implementing.75 Treat `operationGuidance` as optional additive advice. Read and consider every76 entry, and follow entries that are applicable and compatible with the built-in77 workflow.7879 Keep both fields separate from CLI-returned state, missing artifacts, tasks,80 progress, `contextFiles`, and the built-in `instruction`. They are not81 evidence of task completion, do not replace the built-in instruction, and do82 not permit bypassing a blocked state. If context conflicts with the built-in83 instruction, an explicit user choice, or a CLI-controlled value, report the84 conflict and preserve the controlling value. If guidance is inapplicable or85 conflicts with those controlling inputs, do not follow it and explain why.86 These are prompt-level behavior contracts, not enforceable checks.87884. **Read context files**8990 Read every file path listed under `contextFiles` from the apply instructions output.91 The files depend on the schema being used:92 - **spec-driven**: proposal, specs, design, tasks93 - Other schemas: follow the contextFiles from CLI output9495 Do not copy `context` or `operationGuidance` verbatim into implementation96 files or planning artifacts unless the user separately asks for that content.97985. **Show current progress**99100 Display:101 - Schema being used102 - Progress: "N/M tasks complete"103 - Remaining tasks overview104 - Dynamic instruction from CLI1051066. **Implement tasks (loop until done or blocked)**107108 For each pending task:109 - Show which task is being worked on110 - Make the code changes required111 - Keep changes minimal and focused112 - Mark task complete in the tasks file: `- [ ]` → `- [x]`113 - Continue to next task114115 **Pause if:**116 - Task is unclear → ask for clarification117 - Implementation reveals a design issue → suggest updating artifacts118 - 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 silently119 - Error or blocker encountered → report and wait for guidance120 - User interrupts1211227. **On completion or pause, show status**123124 Display:125 - Tasks completed this session126 - Overall progress: "N/M tasks complete"127 - If all done: suggest archive128 - If paused: explain why and wait for guidance129130**Output During Implementation**131132```133## Implementing: <change-name> (schema: <schema-name>)134135Working on task 3/7: <task description>136[...implementation happening...]137✓ Task complete138139Working on task 4/7: <task description>140[...implementation happening...]141✓ Task complete142```143144**Output On Completion**145146```147## Implementation Complete148149**Change:** <change-name>150**Schema:** <schema-name>151**Progress:** 7/7 tasks complete ✓152153### Completed This Session154- [x] Task 1155- [x] Task 2156...157158All tasks complete! You can archive this change with `$openspec-archive-change (Codex) or /openspec-archive-change (other agents)`.159```160161**Output On Pause (Issue Encountered)**162163```164## Implementation Paused165166**Change:** <change-name>167**Schema:** <schema-name>168**Progress:** 4/7 tasks complete169170### Issue Encountered171<description of the issue>172173**Options:**1741. <option 1>1752. <option 2>1763. Other approach177178What would you like to do?179```180181**Guardrails**182- Keep going through tasks until done or blocked183- Always read context files before starting (from the apply instructions output)184- If task is ambiguous, pause and ask before implementing185- If implementation reveals issues, pause and suggest artifact updates186- Keep code changes minimal and scoped to each task187- Update task checkbox immediately after completing each task188- Pause on errors, blockers, or unclear requirements - don't guess189- When a task needs work beyond what the spec describes, surface the added scope and pause - never silently narrow, defer, or simplify away specified behavior190- Only mark a task `- [x]` when its specified behavior is fully implemented, not when it is partially done or deferred191- Use contextFiles from CLI output, don't assume specific file names192- Do not use context or operation guidance as proof that a task is complete193- Apply relevant project context; report conflicts with controlling workflow inputs194- Consider every guidance entry; explain any inapplicable or conflicting advice195- Do not copy runtime context or operation guidance into implementation files or planning artifacts196- Preserve CLI-controlled blocked/ready/all-done behavior and completion criteria197198**Fluid Workflow Integration**199200This skill supports the "actions on a change" model:201202- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions203- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly