openspec-apply-change

When implementing an OpenSpec change, the system pauses safely on blocked states or unclear requirements. It reads context files from the CLI output and provides session-oriented progress reporting to show exactly what is being worked on.

Schema-driven change management handles partially completed states by checking schema status and progress, then fetching dynamic apply instructions. It continues work through pending tasks and suggests the right next step for blocked or completed states.

Yes, you need the OpenSpec CLI to automate workflow progress tracking. The system must call the CLI to determine schema status and retrieve apply instructions in JSON format before reading context files and executing tasks.

The best way to manage context files during change implementation is reading every file path returned by OpenSpec instructions. This context-driven approach ensures minimal, scoped code changes while updating the task checklist.

OpenSpec change implementation pauses during task execution when it encounters blocked states or unclear requirements. This safe guidance mechanism prevents guesswork by stopping execution and providing the right next suggestion.