openspec-apply-change

Automating OpenSpec change implementations involves guiding change selection, checking statuses, and applying tasks via the openspec CLI. The workflow reads context files, updates task completion markers, and reports progress incrementally.

To continue a blocked OpenSpec implementation, the skill checks the current change status and handles blocked states by providing clear prompts. It reads existing instructions and context files to resume task execution safely.

Yes, the openspec CLI is required to apply change tasks. The skill depends on this command-line interface to read status files, analyze changes, and update task completion markers during the implementation workflow.

Task automation handles ambiguous OpenSpec changes by issuing interactive prompts. When a change lacks clear direction, the skill guides the user through safe, incremental implementations rather than guessing the intended action.

Yes, you can generate progress updates for OpenSpec workflows. The skill outputs standardized implementation progress reports detailing completed tasks and current states, which are suitable for archiving or resuming work later.

The best way to manage end-to-end OpenSpec change application is using a guided workflow that selects changes, analyzes context, applies tasks incrementally, and updates completion markers to track status from start to all_done.