openspec-apply-change

Automate OpenSpec change execution by guiding selection, running status checks via the openspec CLI, and implementing tasks step-by-step with dynamic instructions. The workflow reads CLI context files, updates task statuses, and manages blocked or completed states for incremental fulfillment across schemas.

Manage incremental task fulfillment in OpenSpec-driven projects by using guided change selection and context-driven implementation. The workflow tracks progress dynamically, updates artifacts across schemas, and handles blocked states to maintain consistency and reduce waste during execution.

Context-driven task implementation with the openspec CLI works by reading provided context files to generate dynamic instructions for each task. It updates task statuses iteratively, presenting progress while handling blocked and completed states across multiple schemas.

Yes, you can execute OpenSpec changes across multiple schemas and artifacts. The workflow supports artifact updates and iterative refinement, guiding users through stepwise task execution while maintaining consistency across schemas during the change implementation process.

Yes, the openspec CLI is required to apply changes and track task progress. The workflow relies on the CLI for guided change selection, status checks, reading context files, and updating tasks throughout the end-to-end execution process.

OpenSpec change workflows get blocked during task implementation when incremental fulfillment conditions are unmet. The workflow handles blocked states by pausing stepwise execution, presenting current progress, and waiting for required context or artifact updates before proceeding to the next task.