openspec-apply-change

Automate spec-driven development task implementation by using a schema-driven workflow that handles task selection, status checking, instruction retrieval, context file reading, and iterative task completion. It requires the openspec CLI to execute and manage the change process.

An OpenSpec change workflow manages development tasks through a schema-driven process that automates task selection, status checking, and context file reading. It ensures adherence to specifications by iteratively completing tasks and updating progress throughout the change lifecycle.

Yes, the openspec CLI is required for execution and interaction with change management. The implementation process depends on the CLI to handle task selection, retrieve instructions, and iteratively complete tasks defined within the specification.

Yes, the workflow supports contextual awareness and can infer or prompt for the correct change if it is not explicitly provided. This allows you to begin implementing tasks at any stage of a change's lifecycle without specifying the name upfront.

Track progress during task implementation through the workflow's automated status checking and iterative task completion features. As the schema-driven workflow executes tasks from the OpenSpec change, it automatically updates progress and handles various states.

Automation is limited by its dependence on the openspec CLI and requires predefined schema-driven workflows to function. It cannot operate without explicit context files and structured task definitions within the OpenSpec change management system.