openspec-apply-change

Automating OpenSpec change implementation is done by coordinating status checks, loading context files, and executing tasks across specs, design, and implementation artifacts. The workflow iterates through pending tasks incrementally until all changes reach completion.

Managing task execution for software engineering changes requires a task-driven workflow that iterates through pending tasks, applies changes incrementally, and marks tasks complete. This approach ensures progress is monitored and handles task completion or pauses fluidly.

Retrieving status and loading context for an OpenSpec change involves identifying the target change, checking its status, and fetching actionable instructions. The workflow reads context files and loads relevant artifacts to display progress and guide implementation.

Applying changes incrementally and pausing task orchestration midway is fully supported. The workflow loops through tasks, applies changes step-by-step, and handles completion or pauses, allowing fluid updates to artifacts before resuming execution.

You do not need to manually specify the change name to start the workflow. You can provide the change name explicitly, or the system can infer the target OpenSpec change automatically before running the apply-change workflow to implement pending tasks.