openspec-apply-change

To implement OpenSpec change tasks, the Skill reads the change status, instructions, and task artifacts, applies pending code updates one by one, and safely updates task progress. It requires the openspec CLI and a valid change context to resolve artifacts and continue spec-driven development.

Spec-driven development workflow involves loading context from task artifacts, implementing changes task-by-task, and updating checkboxes to track progress. This Skill manages the workflow by resolving dependencies, handling blockers, and pausing cleanly when requirements are ambiguous before continuing.

To resume a partially completed OpenSpec change, provide the change name or a partial hint. The Skill identifies the correct active change, inspects schema status and task progress, loads the exact context files required, and applies the remaining tasks to continue implementation.

Yes, the openspec CLI is required to apply spec-driven changes. The Skill depends on the CLI and a valid change context to resolve artifacts, handle blockers, and update task status safely during task implementation workflows.

When task requirements are ambiguous or blocked during implementation, the Skill pauses cleanly without making incorrect code updates. It inspects workflow status and context files to report the blocker clearly, ensuring safe task-by-task completion.

Yes, you can inspect schema status and task progress before making code updates. The Skill checks the exact context files required and workflow status to ensure all dependencies are resolved prior to applying any spec-driven implementation changes.