openspec-apply-change

You can automate OpenSpec change tasks by using a CLI workflow that coordinates task status, reads context files, and updates execution progress. It guides you from change selection through task implementation, handling blocked, in-progress, and completed states automatically.

Progress tracking for spec-driven changes works by reading context files and updating task status within change files. The system inspects current states via the CLI, ensuring blocked, in-progress, or completed tasks are accurately reflected throughout the implementation workflow.

Yes, the OpenSpec CLI is required to apply changes and track task status. The workflow depends on the CLI to inspect current status, fetch implementation instructions, read necessary context files, and update task progress in the change files.

The best way to handle blocked or in-progress tasks in an OpenSpec workflow is using an automated apply flow. It manages state transitions by fetching instructions and updating change files, streamlining the process for teams automating spec-driven changes.

To start implementing a change with multiple task states, provide a change name or let the system infer one, then run the apply flow. The workflow reads context, fetches instructions, and coordinates execution across blocked, in-progress, and completed tasks.

Manually implementing OpenSpec changes leads to errors because tracking task status and reading context across multiple files is tedious. Automating the end-to-end application ensures progress updates and state handling are managed correctly without manual intervention.