openspec-apply-change

Automating OpenSpec changes is done by scoping to your local workspace, selecting a named change, running status checks, and executing tasks via the npx openspec command to apply code changes automatically.

When an OpenSpec change is blocked or completed, the workflow detects the state and provides actionable prompts to guide your next steps, preventing redundant execution and ensuring proper task progression.

To apply a named OpenSpec change, invoke the workflow using npx openspec, select your desired change from the local workspace, pass the status checks, and follow the dynamic prompts to execute the required implementation tasks.

Yes, using npx openspec is required because this workflow strictly enforces execution through the command-line interface to ensure changes are applied consistently and task automation progresses correctly.

Handling missing artifacts during OpenSpec task execution involves relying on the workflow's built-in status checks, which detect missing artifacts and provide context-driven instructions to guide you through the required setup.

Manual selection is required because the workflow scopes to changes within your local workspace, guiding you through choosing the specific named change to ensure the correct context and tasks are applied dynamically.