openspec-change-implementation

OpenSpec change implementation automates the process of applying approved proposals by loading proposal and task definitions, executing the specified changes, running tests, and generating execution logs for traceability. Approve your proposal first, then run the implementation to apply changes and capture test results.

The implementation skill runs tests after executing changes and records execution evidence including test results, logs, and updated artifacts. This creates a complete audit trail proving that changes were applied correctly and meet requirements.

Yes, OpenSpec implementation is designed for Level 0-1 workflows. It enforces approval gates, follows the exact task sequence defined in your proposal, and automates the entire change execution pipeline with status updates.

You need proposal.md and tasks.md files that define your approved changes. The skill loads these definitions and executes the tasks in sequence, then produces implemented code and test results as output artifacts.

Yes, the skill enforces an approval gate—changes only execute after proposals are formally approved. This ensures traceability and prevents unapproved modifications from entering your workflow.