openspec-apply-change

Automating OpenSpec change application involves guiding change selection, assessing status, and executing tasks sequentially. This workflow reads context from generated artifacts and updates task checkboxes to ensure consistent progression from pending to complete.

Managing blocked tasks in a spec-driven workflow requires safe guardrails and dynamic prompts. The system identifies blockers during task execution, pauses progression, and requests user intervention to resolve dependencies before continuing.

Yes, applying changes to proposals and designs requires the OpenSpec CLI. The CLI orchestrates the end-to-end workflow by reading context files, retrieving instructions, and driving task progression across artifacts with minimal manual intervention.

Continuing an in-progress OpenSpec change starts with selecting the active change and assessing its status. The system reads existing context files, identifies pending tasks, and resumes task-by-task execution until all implementations are complete.

Validating completed OpenSpec changes is supported by assessing task status and reading implementation artifacts. The system checks task checkboxes, confirms completion states, and provides clear prompts if any tasks remain incomplete or blocked.

Automating spec-driven change management relies on generated context artifacts and requires manual input when blockers occur. It cannot resolve missing dependencies independently and functions only within the boundaries of the OpenSpec CLI workflow.