openspec-apply-change

Applying OpenSpec changes involves selecting a change, checking status, reading context, and implementing tasks with progress tracking. The workflow enforces CLI-driven execution, updates task statuses, and handles blocked or all_done states across schemas.

Task automation tracks OpenSpec progress by updating task checkboxes as work proceeds and reporting status changes. It handles blocked and all_done states across schemas, ensuring consistent execution and visibility throughout the change implementation lifecycle.

The CLI workflow for OpenSpec changes guides users through selecting a change, reading context files, and implementing tasks. It enforces repeatable execution, updates task statuses dynamically, and reports progress across multiple schemas.

Yes, the OpenSpec workflow explicitly handles blocked task states. When implementation tasks encounter blockers, the CLI workflow tracks these states, updates progress accordingly, and reports the status across schemas to maintain visibility.

To start applying an OpenSpec change, provide the change name and run the OpenSpec apply workflow. The system reads the relevant context files, checks the current status, and guides you through implementing tasks with automated progress tracking.

Yes, a CLI environment is required because the OpenSpec apply workflow enforces a CLI-driven workflow. This ensures repeatable execution for selecting changes, reading context, implementing tasks, and tracking progress across schemas.