openspec-apply-change

You can automate OpenSpec change implementation by using a skill that orchestrates status checks, context extraction, and task application across proposal, spec, and design artifacts. It coordinates end-to-end execution by dynamically applying tasks and tracking progress as the change evolves.

Managing multiple active OpenSpec changes is handled by inferring changes from context and providing guided prompts when ambiguous. The automation skill selects and applies tasks from the inferred change, tracking progress dynamically across the active workflows.

Yes, the openspec CLI is required to apply change tasks. The automation requires the CLI to execute status checks, read context artifacts, and dynamically apply tasks across the change workflow.

Task automation tracks progress by reading and modifying context artifacts like proposals, specs, designs, and tasks. It dynamically adapts instructions and updates task progression as the change state evolves throughout the implementation workflow.

Yes, when OpenSpec changes are ambiguous, the automation provides guided prompts to infer the correct context. It then proceeds with code implementation by applying tasks from the selected change while handling context ingestion and status checks.

OpenSpec change management requires coordination because implementation spans multiple tools, artifacts, and task states. Automating this orchestration ensures status checks, context reads, and task updates are executed consistently across the entire workflow.