openspec-apply-change

OpenSpec change implementation tasks are automated by selecting or inferring the target change, checking its status, and loading the appropriate context to drive schema-aware task execution. The system presents concrete tasks and tracks progress until completion or a blocker arises.

Context-driven execution reads OpenSpec workflow context files to provide deterministic task execution and progress tracking. It surfaces remaining tasks, current schema, and dynamic instructions based on the real-time change state.

When ambiguous requirements or errors occur during change integration, guardrails prompt for clarification on ambiguous requirements and automatically pause on errors. This enables a smooth workflow for iterative changes without failing silently.

Yes, you can apply multiple tasks sequentially within a single OpenSpec change workflow. The system guides you to start implementation, continue tasks, or work through a sequence of tasks until the change is fully complete.

No, you do not need to manually specify the target change name to start task automation. You can provide the change name explicitly or let the system infer it from the current conversation context.

Automated OpenSpec change application pauses when a blocker arises or when errors occur during task implementation. It requires schema-aware context files to function correctly and will prompt for clarification rather than guessing on ambiguous requirements.