openspec-apply-change

OpenSpec change workflows guide you from selecting a change through applying tasks and tracking progress. The workflow checks status, reads context files like proposals and specs, and updates YAML task artifacts to track real-time progress and handle blockers.

You track OpenSpec task status by parsing CLI outputs and updating YAML task artifacts to reflect completed work and blockers. The workflow provides real-time progress updates, shows remaining tasks, and proposes artifact updates to keep the collaborative development environment fluid.

The OpenSpec apply change workflow pauses gracefully when encountering blockers during task execution. It proposes updates to YAML task artifacts to document the blocker, allowing you to maintain workflow fluidity and resume the controlled task loop when the issue is resolved.

Yes, interacting with the openspec CLI is required to apply changes and execute pending tasks. The workflow depends on parsing CLI outputs to fetch apply instructions, read context files like tests and implementation docs, and manage the controlled task loop in a collaborative development environment.

Applying an OpenSpec change reads relevant context files including proposals, specs, design, tasks, tests, implementation, and docs. These files provide the necessary context to execute pending tasks in a controlled loop and show dynamic guidance for remaining work.