openspec-apply

You implement approved OpenSpec changes by executing the workflow defined in tasks.md to apply scope-limited edits sequentially. The process reads proposal.md, design.md, and tasks.md, updates task checklist states, and performs a final verification against acceptance criteria.

The OpenSpec change implementation process reads approved versioned proposals and executes defined task checklists sequentially. It ensures controlled, scope-limited codebase edits while tracking progress and validating final results against specified acceptance criteria.

To execute tasks without missing acceptance criteria, follow the tasks.md checklist sequentially to perform minimal required edits. The implementation process strictly adheres to the requested scope and runs a final validation check after all tasks are completed.

Yes, you can apply design.md specifications during repository updates when the file is present. The implementation workflow reads design.md alongside proposal.md and tasks.md to guide controlled codebase edits and ensure alignment with the approved change scope.

Yes, an approved proposal is required before running change management tasks. The implementation workflow specifically applies to post-approval scenarios, reading the approved changes/<id>/proposal.md to execute controlled, scope-limited edits across the project codebase.

Automated OpenSpec change implementation is limited to executing approved, scope-limited edits defined in tasks.md. It does not generate the proposal or design files itself, and relies entirely on pre-existing acceptance criteria and task definitions to perform final verification.