openspec-apply-change

Automate OpenSpec changes by using a status-driven workflow that detects the target change, reads context files, iteratively applies tasks, and updates task statuses through state transitions like blocked and all_done.

Manage blocked OpenSpec tasks by reading the current change state, determining the schema, handling blockers iteratively, and updating task statuses to reflect state transitions while prompting the user when context is ambiguous.

Yes, you can infer the target OpenSpec change name automatically from context, or specify it manually, to begin guiding the implementation and progression of changes step by step.

Track OpenSpec task status through a task implementation loop that reads current state, applies tasks iteratively, marks progress, handles blockers, and ensures state transitions like all_done are updated.

Yes, applying and tracking OpenSpec changes requires interaction with the OpenSpec CLI to read context files, determine schema, update task statuses, and handle state transitions end-to-end.

OpenSpec change workflows prompt for context when information is unclear or ambiguous, ensuring artifact-aware updates and correct implementation decisions before proceeding with task state transitions.