openspec-apply-change

To automate OpenSpec change tasks, you can use a guided workflow that determines the current change state, loads relevant context, and applies tasks while updating task status. This requires the openspec CLI to manage execution end-to-end.

The best way to track progress when applying OpenSpec changes is to use a workflow that queries OpenSpec for schema, tasks, and progress. It keeps a running log of implementation progress directly in the CLI for auditing.

Yes, you need the openspec CLI to manage and execute change tasks. The CLI is required to query status, load context files, and handle progressive task implementation during the OpenSpec change workflow.

Status awareness works by querying OpenSpec for schema, tasks, and current progress when continuing an OpenSpec change. It handles blocked or all-done states by providing clear prompts and showing the next actions required.

To handle ambiguous changes or blocked states in OpenSpec, the guided workflow provides interactive guidance. It prompts for clarification on ambiguous changes and outputs clear prompts for blocked or completed states to guide the next action.

A limitation of automating OpenSpec change management is its dependency on the openspec CLI and context files. Without proper context loading, the dynamic instructions cannot effectively guide progressive task implementation or resolve blocked states.