openspec-apply-change

Implementing OpenSpec changes is automated by this Skill using the `/apply <change-name>` command, which manages execution, reads context files, and tracks progress. It provides a structured approach to handle task execution efficiently within spec-driven workflows.

Tracking OpenSpec change status is handled natively by monitoring the implementation process, displaying remaining tasks, and updating states. The Skill checks progress and guides task completion to ensure all changes are executed with minimal manual overhead.

Yes, the openspec CLI is required as a dependency to automate task execution and change management. The Skill relies on the CLI to handle various implementation states, including blocked, all_done, and in-progress scenarios.

Spec-driven workflow implementation handles blocked and in-progress states by monitoring status and providing clear outputs during pause scenarios. It ensures that task execution resumes correctly and updates task status upon completion.

Yes, managing software development changes is streamlined by guiding users through task completion with minimal changes. The Skill parses required context files, automates implementation, and updates task status automatically.

OpenSpec task implementation stalls in a blocked state when dependencies or contextual requirements are unmet. The Skill monitors these implementation states, providing clear outputs to help users identify and resolve blocking issues before resuming.