openspec-apply-change

To execute spec-driven change proposals end-to-end, you need a tool that orchestrates task selection, tracks progress, and validates artifacts. This skill automates that workflow by reading context files and applying dynamic state-based instructions for implementation.

Tracking task execution status during test-driven development requires reading schema states and updating task progress dynamically. This skill provides continuous feedback by inspecting current status, showing remaining tasks, and validating artifacts before proceeding.

Yes, applying changes across proposal, design, and test contexts requires the openspec CLI to be installed and accessible. The skill reads status and context files directly through the CLI to validate artifacts and orchestrate dynamic execution instructions.

Yes, you can update artifacts and specs during an ongoing change implementation. The skill supports a fluid workflow by allowing context file updates and handling tasks across proposals, specs, design, tests, and implementation before the change reaches completion.

Dynamic state-based instruction for spec-driven implementation works by reading the current schema and context files to generate targeted task guidance. The skill validates existing artifacts and adjusts execution instructions based on the real-time progress of the change.

Change implementation stalls when switching between tasks, tests, and documentation if context files are not properly validated. The skill prevents this by inspecting status, validating artifacts, and applying dynamic instructions across all execution phases.