openspec-apply-change

To implement OpenSpec changes, you select an active change, read its status and apply instructions, and execute task updates against the correct planning artifacts. The workflow validates context files and task lists to ensure spec-driven changes are applied safely.

Spec-driven task execution handles blocked or partially completed changes by pausing the workflow, prompting for clarification, or recommending the next OpenSpec action. It inspects the current schema and loads relevant artifacts to resume work methodically.

Yes, you need the openspec CLI to apply change-scoped constraints. The CLI inspects changes, loads instructions, and completes or pauses work with validation-aware guardrails to ensure task execution follows context files correctly.

The best way to continue a partially completed OpenSpec change is to inspect the current schema, load the relevant planning artifacts, and implement the remaining tasks. The assistant selects the right active change and updates progress as each step completes.

Spec-driven implementation requires reading status and apply instructions to ensure task updates follow change-scoped constraints. This validation-aware approach prevents incorrect modifications by checking context files and task lists before executing.

Yes, OpenSpec change implementation handles ambiguous requests by listing available changes when the selection is unclear. It chooses the right active change from conversation context or prompts you to specify which change to apply.