openspec-apply-change

To implement OpenSpec tasks safely, retrieve concrete apply instructions via the CLI, parse the JSON output to identify required context files, and read those files before editing any code. This ensures your task automation stays aligned with spec-driven development artifacts and workflow schemas.

Progress tracking during spec-driven development changes works by iterating through a task list, marking each task complete in the workflow orchestration loop, and pausing safely when encountering blocked, unclear, or error states to suggest next actions.

Selecting the correct OpenSpec change involves inferring or prompting for the active change based on conversation context, then checking schema status to understand the available workflow artifacts and pending tasks before implementation begins.

OpenSpec task automation pauses safely on blocked, ambiguous, or failed steps during workflow orchestration. It executes a loop that marks completed tasks and suggests next actions when issues are encountered, preventing unguided progress on unclear states.

Before applying changes in a spec-driven development workflow, you need to check schema status and retrieve context files by running openspec status and openspec instructions apply. This verifies the workflow schema and loads required artifacts before task iteration begins.

OpenSpec CLI integration applies pending tasks by running openspec instructions apply with JSON parsing to retrieve the task list and context files, then iterating through tasks while reading required artifacts before editing and marking completions.