openspec-apply-change

Automating OpenSpec change application involves coordinating status checks and driving iterative task execution until completion. The process reads status, instructions, and context files to guide implementation, handling blocked or completed states automatically.

Managing change status and context files requires workflow coordination across the apply cycle. Reading status files and schema allows the system to select tasks, apply changes iteratively, and update artifacts as design issues surface during implementation.

Yes, the openspec CLI is required to apply changes. It reads the necessary status, instructions, and context files to drive task execution, report real-time progress, and enforce guards for blocked states during the code-change workflow.

Yes, reverse-safe iteration allows you to pause, resume, and update artifacts when design issues surface during implementation. The workflow coordinates status checks to safely handle blocked states and continue task progression later.

Task workflows get blocked when status checks identify incomplete dependencies or design conflicts in the context files. The workflow uses guards to halt execution, requiring you to resolve the blocked state before resuming iterative code-change application.