openspec-apply-change

Automating OpenSpec changes end-to-end involves guiding change selection, checking status, and incrementally executing tasks. The workflow tracks progress by updating task checkboxes and applying minimal, auditable code edits through the OpenSpec CLI.

Managing blocked states in a spec-driven workflow requires strict state handling during task execution. The system checks change status, pauses implementation when blocked, and reads context files to ensure progress reporting remains accurate and auditable.

Selecting and applying active OpenSpec changes is handled through guided change selection. The workflow automatically determines which changes are active and needed, then proceeds with incremental implementation by looping through deterministic task instructions.

Yes, the OpenSpec CLI is required to apply spec-driven changes. The workflow depends on the CLI to coordinate change selection, execute deterministic task instructions, and maintain strict state handling with minimal, auditable code edits.

Incremental implementation for OpenSpec task lists works by applying tasks in a loop. As each task completes, the workflow marks it done in the task list, updates progress reporting, and applies minimal code edits to ensure an auditable execution trail.

Tracking progress and archiving completed changes in an OpenSpec workflow is achieved through status-driven checks. The system updates task-checkboxes, handles done states, and archives progress, ensuring all applied changes are tracked and auditable.