openspec-apply-change

Implementing OpenSpec change requests requires selecting the correct active change, reading its schema and task progress, and executing pending work in order. This workflow updates task checkboxes as each item is completed safely and consistently.

Status-driven workflow automation for partially started spec changes inspects the schema, task progress, and dynamic instructions before making edits. It identifies the correct change from context or the OpenSpec change list and guides remaining implementation tasks until completion or blockage.

Yes, executing spec-driven implementation workflows requires the openspec CLI to inspect changes, load context files, and update task status safely and consistently. The CLI provides the artifact-aware task completion and progress tracking needed for implementation.

Managing progress tracking with multiple active OpenSpec changes relies on change selection logic that picks the correct active change from context or the OpenSpec change list. It then reads required files and guides remaining implementation sequentially.

Handling blocked-state conditions during change implementation involves inspecting status and instructions before executing pending work. The workflow guides tasks one by one until completion or blockage is encountered, safely pausing execution.

Yes, artifact-aware task completion for spec-driven workflows operates with no external dependencies. It uses the openspec CLI to load context files and update task status, ensuring consistent progress tracking without additional packages.