openspec-apply-change

You can automate OpenSpec change implementation by specifying the change name to initiate a guided workflow. The process reads apply instructions, context files, and progress status to dynamically drive subsequent actions and track tasks until completion.

A spec-driven workflow uses specification documents to drive code modification and task tracking. It supports iterative updates, pausing, resuming, and clear outputs with guardrails to ensure changes are implemented accurately across multiple artifacts.

Yes, the workflow supports pausing, resuming, and iterative updates during OpenSpec change implementation. It reads progress status and context files to dynamically determine subsequent actions, allowing you to stop and restart without losing track of completed tasks.

The OpenSpec CLI workflow handles conditional states including blocked and all_done. When a change is blocked, the workflow reads context files and apply instructions to provide dynamic guidance on resolving the issue before proceeding.

You mark tasks complete by following the guided steps within the change implementation workflow. The system tracks progress across multiple artifacts, updating the status of each task until the overall change reaches the all_done state.

Using an automated workflow for feature rollouts reduces manual coordination and errors. It orchestrates the end-to-end implementation process by automatically reading instructions, checking status, and tracking tasks across all related artifacts.