openspec-apply-change

Automating OpenSpec change execution involves orchestrating status checks, reading context files like proposals and specs, and implementing tasks stepwise until completion. This skill guides the workflow by parsing progress and updating task checkboxes as each item finishes.

Change-driven workflow orchestration automates guided task execution by parsing status JSON to verify schema and progress. It manages implementation by loading relevant context files, adapting guidance based on outcomes, and announcing blocked or all-done states to the user.

Applying a named OpenSpec change starts with announcing the selected change, then parsing the status JSON to verify the schema and current progress. The workflow reads context files to drive implementation and iteratively marks pending tasks as complete.

Yes, automation can manage OpenSpec changes with blocked tasks. The workflow includes guardrails that trigger a graceful pause upon encountering ambiguity or blockers, proposing options to the user while maintaining safe, minimal changes before resuming execution.

When OpenSpec change implementation reaches completion, the workflow presents a clear summary of the executed tasks and suggests archival steps. This completion readiness ensures the change-driven development cycle is properly closed and documented.