openspec-apply-change

OpenSpec change implementation is automated by selecting the target change, validating its current status, loading contextual artifacts, and driving task execution iteratively until completion or blockage. The workflow applies dynamic instructions based on the available schema and artifacts.

An OpenSpec change workflow is a structured process for implementing tracked engineering tasks iteratively. You need it when changes are logged as OpenSpec changes requiring safe, auditable progress, contextual instructions, and continuous status verification before applying modifications.

Applying tasks from an OpenSpec change safely requires fetching the apply instructions, loading the necessary context files, and following dynamic safety checks. This ensures auditable progress by validating the change status and handling blocked or completed states before executing.

Yes, OpenSpec change execution supports dynamic instructions based on the current state and available artifacts. The system retrieves the change status to understand the schema and artifact location, then adjusts the task implementation and progress reporting accordingly.

If an OpenSpec change is blocked or already completed, the workflow includes safety checks to handle these states. The system validates the change status during selection and stops execution or prevents re-application to ensure safe, auditable progress without overwriting finished work.

No external dependencies are required to orchestrate OpenSpec changes. The workflow operates independently to select changes, validate status, load context files, and apply tasks, relying solely on the OpenSpec schema and the available artifact locations within your engineering environment.