openspec-apply-change

You can automate applying OpenSpec changes by providing the change name to begin the workflow. The system guides change selection, reads CLI status outputs, implements tasks with minimal code changes, and updates task checkboxes upon completion.

The best way to continue interrupted OpenSpec change implementation is to assess the current status using the OpenSpec CLI. The workflow adapts by reading existing progress, determining remaining tasks, and resuming work from the exact point of interruption.

Change management automation handles blocked or completed tasks by dynamically parsing CLI outputs and prompting the user with clear instructions. It updates task checkboxes when completed and suggests artifact updates if design issues surface during implementation.

Yes, you can use this OpenSpec workflow before all artifacts are fully complete. It works as an actions component on a change, allowing you to apply tasks after partial work, suggest artifact updates if design issues surface, and continue until completion.

Yes, the OpenSpec CLI is required as it provides the dynamic task parsing, status assessment, and context files needed for automation. The workflow reads these CLI outputs to determine the current schema, progress, and remaining work to implement.