openspec-apply-change

To automate OpenSpec task implementation, apply the named change to iterate through pending tasks, read context files, write minimal scoped code, and update the task artifacts automatically. The workflow queries the openspec CLI for status and schema-specific instructions to drive the loop.

Task-driven code implementation handles blocked or ambiguous tasks by pausing the workflow and prompting the user for clarification. It processes pending tasks iteratively but stops automatically marking progress when a task lacks clear instructions or context.

Yes, you need the openspec CLI to fetch status and apply instructions for the change. The implementation workflow requires querying the CLI to read context files, follow schema-specific guidance, and update the tasks file to mark progress.

The best way to move from an OpenSpec change definition to concrete code is using an automated apply workflow that discovers context, selects the change, and implements pending tasks one by one. This removes orchestration friction so developers can focus on minimal code changes.

Yes, the change selection and discovery mechanism can infer the active OpenSpec change name automatically or prompt you to select from a list. It announces the selected change and any override mechanism before fetching apply instructions.

Your OpenSpec apply workflow pauses before completing all pending tasks when it encounters blocked or ambiguous items requiring user input. It stops the task-driven implementation loop to prevent incorrect code changes and waits for your guidance.