openspec-apply-change

You can automate applying OpenSpec changes by selecting a specific change, validating its schema, and orchestrating task-level implementations step by step. The automation enforces guardrails to keep modifications minimal and reports progress after each task completes.

When an OpenSpec change workflow encounters a blocked state, the automation pauses and asks for clarification if requirements are unclear. It handles blocked, all_done, and active task states dynamically to ensure smooth task-level execution.

Yes, you can infer the active OpenSpec change from conversation context. If a change name is omitted, the automation infers it from context or prompts you to choose via CLI disambiguation prompts before proceeding.

To ensure change management tasks stay minimal during AI-assisted implementation, the automation enforces strict guardrails. It reads context files, asks for clarification on unclear requirements, and orchestrates step-wise execution to prevent unnecessary modifications.

The best way to handle task automation for OpenSpec changes with multiple active tasks is using a context-aware implementation loop. It validates schemas, orchestrates tasks sequentially, and reports progress after each step until reaching the all_done state.