openspec-apply-change

Automating OpenSpec change application involves selecting a specific change, checking its status, reading context files like proposals and specs, and executing tasks with progress tracking. This workflow guides implementation until completion using minimal, scoped code changes.

The best way to manage context files is by parsing apply-instruction artifacts such as proposals, specs, design, and tasks. This ensures schema-driven instructions are followed for minimal, scoped code modifications during task implementation.

Yes, you can use CLI tools to drive OpenSpec workflows by interactively selecting changes and checking status. This automates the process of reading context files and implementing tasks until all items are completed.

Change-management workflows handle blocked and all-done states by providing clear guardrails and prompts for next steps. This ensures task automation stops or redirects appropriately when implementation cannot proceed or is fully completed.

Yes, you need apply-instruction artifacts like proposals, specs, design documents, and tasks to execute OpenSpec task automation. These context files provide the schema-driven instructions required for scoped code changes and progress tracking.