openspec-apply-change

Spec-driven development task implementation is automated by reading context files and executing tasks defined within an OpenSpec change. The process selects tasks, checks their status, retrieves instructions, and iteratively applies changes to systematically update the project.

Applying OpenSpec changes to a development workflow is best handled by retrieving instructions and context files to systematically implement each defined task. The automated process infers or prompts for the specific change, ensuring all specification requirements are met.

Yes, the openspec CLI is required to implement change tasks. The implementation process relies on CLI interaction, specifically using openspec status and openspec instructions apply commands to understand the workflow and retrieve the required artifacts.

Task selection and progress tracking work by iteratively checking task status and retrieving instructions. The process reports on completed tasks, remaining tasks, and overall progress to ensure all specification requirements are systematically met.

Yes, this approach supports schema types beyond spec-driven workflows. The implementation process applies changes based on various defined specifications, allowing you to automate task execution and status updates across different schema formats.