openspec-apply-change

You can manage OpenSpec changes end-to-end by fetching active changes, checking status, pulling apply instructions, and implementing tasks. The workflow enforces guardrails like blocking states and ambiguity prompts to ensure scoped, traceable execution from discovery to completion.

Change orchestration prompts users for clarifications when ambiguity is detected during task implementation. This guardrail ensures minimal, scoped changes by resolving uncertainty before proceeding with the workflow execution.

Yes, you can track progress and surface verification outcomes throughout the OpenSpec change workflow. The system provides clear failure modes for blocked states and maintains transparency from initial selection through task completion.

The best way to start an OpenSpec change workflow is to fetch active changes, resolve any ambiguity, and select a target change for execution. This coordinated planning phase sets up the subsequent status checks and task implementation steps.

No external dependencies are required to orchestrate OpenSpec changes. The skill operates independently to fetch changes, check status, retrieve instructions, read context files, and implement tasks with built-in guardrails for blocking states and progress tracking.

Your OpenSpec change workflow enters a blocked state when guardrails detect conditions that prevent safe execution, such as ambiguity or scope violations. The system provides clear failure modes and prompts for clarifications to help you resolve the block and continue.