spectra-apply

To automate Spectra change execution, invoke the spectra-apply workflow to select a change, run preflight checks, read context, and implement tasks until completion. It enforces a file-based task tracker to maintain a single source of truth throughout the process.

To resume an in-progress Spectra change, the automation reads the file-based task tracker to identify pending tasks, unparks changes if needed, adds them back to in-progress, and continues implementing tasks until finalization.

Yes, the spectra CLI is a required dependency to automate change management. The workflow relies on it to check status, fetch apply instructions, perform preflight handling, and track progress via the file-based task tracker.

File-based task tracking works by maintaining a single source of truth for progress during Spectra change application. The automation reads and updates this tasks file to handle in-progress states, parked changes, and finalization or pausing as needed.

Yes, you can pause task implementation midway through a Spectra change workflow. The automation handles paused states by updating the file-based task tracker, allowing you to resume the in-progress change later without losing context or progress.

The best way to handle parked changes in a Spectra workflow is to let the automation unpark them and add them to in-progress automatically. It checks status, retrieves apply instructions, and updates the task tracker before implementing the tasks.