openspec-apply-change

Spec-driven change management is the process of implementing updates through structured proposal, spec, design, and task artifacts. This Skill orchestrates that workflow by loading context, checking status, and guiding task execution to keep implementation synchronized.

Yes, you can resume an in-progress task implementation after a blocker. The Skill identifies blocked or partial states, reloads required context files, and pauses cleanly when ambiguity appears, allowing you to recover and continue the spec-driven workflow.

Yes, the openspec CLI is required to apply change tasks. The Skill depends on the CLI to read implementation status, load apply instructions, resolve context files, and handle blocked, partial, and complete workflow states.

The best way to manage workflow orchestration for spec-driven development is to automate status checks and context loading. This Skill orchestrates the workflow by reading schema state, resolving context files, and guiding task iteration sequentially.

Task synchronization works by updating task checkboxes as implementation progresses. The Skill iterates through remaining tasks, verifies the workflow state, and keeps implementation progress aligned with the OpenSpec change artifacts.